From 4f3d113a433308eaa518c19718e0a3854a56be96 Mon Sep 17 00:00:00 2001 From: Abo Date: Mon, 15 Aug 2022 18:02:03 +0200 Subject: [PATCH 1/2] Update guidelines for demos (#1055) --- docs/contributing/publishing-a-new-release.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/contributing/publishing-a-new-release.md b/docs/contributing/publishing-a-new-release.md index ae02acd..474120f 100644 --- a/docs/contributing/publishing-a-new-release.md +++ b/docs/contributing/publishing-a-new-release.md @@ -24,7 +24,7 @@ Now [create the release in GitHub](https://docs.github.com/en/repositories/relea - Click "Releases" - Click "Draft a new release" - Click "Choose a tag" -- Type the title, select the previous tag, click "Auto-generate release notes" and click "Preview" to verify; you should have a list with the changes from the previous release, edit as required: +- Type the title, select the previous tag, click "Auto-generate release notes" and click "Preview" to verify; you should have a list with the changes from the previous release, edit as required and remember to include the list below as explanation: - `+`: new feature - `*`: bug fix - `!`: feature modification @@ -32,3 +32,6 @@ Now [create the release in GitHub](https://docs.github.com/en/repositories/relea - Click "Publish release" - It's done, zip and tar.gz files are automatically assigned to the release - The new release appears in the Code home page, with the changelog in the release page itself. + +Now create a release for the [demos](https://github.com/abap2xlsx/demos) repository as well: use the same process and tag the latest commit available at the time the main library is released, to ensure users will always have a matching set of demo programs. + From eb7d8da540bbdbf89972d301b5260b5d533523db Mon Sep 17 00:00:00 2001 From: Abo Date: Mon, 22 Aug 2022 10:18:28 +0200 Subject: [PATCH 2/2] Update publishing-a-new-release.md (#1057) ideally we shoudl run ZDEMO_EXCEL_CHECKER during the review process of each PR for both the main library and the demos, but as a safety net also before releasing a new version --- docs/contributing/publishing-a-new-release.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/contributing/publishing-a-new-release.md b/docs/contributing/publishing-a-new-release.md index 474120f..6db8e4d 100644 --- a/docs/contributing/publishing-a-new-release.md +++ b/docs/contributing/publishing-a-new-release.md @@ -1,6 +1,7 @@ # Publishing a new release Let's create a release from time to time, every 1 or 2 months for instance, to contain enough changes, but not too much. +Before beginning, you should ensure that ZDEMO_EXCEL_CHECKER (in the demos repo) shows all green checkmarks. Below are the notes taken while publishing the release `7.16.0`.