You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/release_steps.md
+35-23Lines changed: 35 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,10 @@ This steps have to be followed always when preparing a new release.
16
16
-[ ] for `geostore`, check if [here](https://maven.geo-solutions.it/it/geosolutions/geostore/geostore-webapp/) is present the version specified. Release procedure is specified in the [Readme.md](https://github.com/geosolutions-it/geostore) file of the project.
17
17
-[ ] for `http_proxy`, check if [here](https://maven.geo-solutions.it/proxy/http_proxy/) is present the version specified. Release procedure is specified in the [Readme.md](https://github.com/geosolutions-it/http-proxy) file of the project.
18
18
-[ ] for `mapfish-print` check if [here](https://maven.geo-solutions.it/proxy/http_proxy/) is present the version specified. Release procedure is specified in the [Readme.md](https://github.com/geosolutions-it/mapfish-print) file of the project.
19
+
-[ ] Check if dependencies of MapStore libraries and geostore libraries are the same (compare `src/pom.xml` in geostore e `pom.xml` in MapStore).
20
+
-[ ] Check if dependencies of the **template projects** are aligned
21
+
-[ ]`project/standard/templates/pom.xml` are aligned as the ones in `pom.xml` of MapStore
22
+
-[ ]`project/standard/templates/web/pom.xml` are aligned as the ones in `product/pom.xml` of MapStore.
19
23
20
24
## New stable branch creation
21
25
@@ -27,32 +31,37 @@ This steps have to be followed always when preparing a new release.
27
31
-[ ] MapStore branch name to use: `YYYY.XX.xx`
28
32
-[ ] use the default value for the other parameters
29
33
-[ ] Wait for the process to complete. At the end:
30
-
- A Pull request will be created to the master
31
-
- A new branch named `YYYY.XX.xx` with fixed versions
34
+
- A Pull request will be created to the master
35
+
- A new branch named `YYYY.XX.xx` with fixed versions
32
36
-[ ] Merge the incoming PR created by the workflow
33
-
-[ ] Create on [ReadTheDocs](https://readthedocs.org/projects/mapstore/) project the version build for `YYYY.XX.xx` (click on "Versions" and activate the version of the branch)
37
+
-[ ] Create on [ReadTheDocs](https://app.readthedocs.org/projects/mapstore/) project the version build for `YYYY.XX.xx` (click on "Versions" and activate the version of the branch)
34
38
-[ ] Run the [`Cut Release Branch`](https://github.com/geosolutions-it/MapStoreExtension/actions/workflows/cut_release_branch.yml) workflow on MapStoreExtension project, indicating:
35
-
-[ ] Use workflow from branch `master`
36
-
-[ ] MapStore branch name to use: `YYYY.XX.xx`
37
-
-[ ] main branch `master` (default)
39
+
-[ ] Use workflow from branch `master`
40
+
-[ ] MapStore branch name to use: `YYYY.XX.xx`
41
+
-[ ] main branch `master` (default)
38
42
-[ ] Update the [QA build](http://build.geosolutionsgroup.com/view/MapStore/job/MapStore/view/MapStore%20QA/job/MapStore2-QA-Build/) to point to the branch created (YYYY.XX.xx)
39
43
40
44
## Before the Release
41
45
42
46
-[ ] Check `pom.xml` dependencies are all in fixed stable versions ( no `-SNAPSHOT` usage release). If not, You use the action [`Update dependencies versions`](https://github.com/geosolutions-it/MapStore2/actions/workflows/update_dependencies_versions.yml) to fix them, setting:
43
-
-[ ] the branch to `YYYY.XX.xx`
44
-
-[ ] the of geostore, http_proxy and mapfish-print versions accordingly with the [MapStore release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars)
45
-
-[ ] Check that [MapStoreExtension](https://github.com/geosolutions-it/MapStoreExtension) repository is aligned and working
47
+
-[ ] the branch to `YYYY.XX.xx`
48
+
-[ ] the of geostore, http_proxy and mapfish-print versions accordingly with the [MapStore release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars)
49
+
-[ ] Merge the PR created after the action avove has been finshed
50
+
-[ ] Check that [MapStoreExtension](https://github.com/geosolutions-it/MapStoreExtension) repository is aligned and working.
51
+
-[ ] Run the [Submodule Update](https://github.com/geosolutions-it/MapStoreExtension/actions/workflows/submodules_update.yml) of [MapStoreExtension](https://github.com/geosolutions-it/MapStoreExtension) to generate the `SampleExtension.zip` to use for testing.
52
+
-[ ] Use workflow from `YYYY.XX.xx` branch
53
+
-[ ] Wait for completition
54
+
-[ ] Download the `Artifacts.zip` that contains `SampleExtension.zip` from the execution of the `checks` action on the branch `YYYY.XX.xx`. This can be used for tests.
46
55
-[ ] Test on QA [https://qa-mapstore.geosolutionsgroup.com/mapstore/](https://qa-mapstore.geosolutionsgroup.com/mapstore/)
47
56
-[ ] Test **everything**, not only the new features
48
57
-[ ] Test the creation of a standard project starting in from the stable branch and with the internal backend, so:
49
-
-[ ]`node ./createProject.js` and insert the entries (for the rest simply press enter:
50
-
- **project name**: `release_project_test`
51
-
- **base branch**: insert the release branch (e.g. `YYYY.XX.xx`)
-[ ]`npm run start:app`, then check that an empty homepage loads correctly
56
65
-[ ] Test [Binary](http://build.geosolutionsgroup.com/view/MapStore/job/MapStore/view/MapStore%20QA/job/MapStore2-QA-Build/) (take the mapstore2-<RELEASE_BRANCH>-qa-bin.zip, from latest build)
57
66
58
67
## Prepare Release
@@ -64,8 +73,8 @@ This steps have to be followed always when preparing a new release.
64
73
- version to fix for the java module, accordingly with [release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) (e.g. `1.7.0`)
65
74
- use the default value for the other parameters
66
75
-[ ] Wait for the process to complete. At the end:
67
-
- a new commit will be added to the release branch tagged as `vYYYY.XX.mm`. This commit will contain the changelog and the updated version of the java modules.
68
-
- a pull request will be created on master with the changelog updates
76
+
- a new commit will be added to the release branch tagged as `vYYYY.XX.mm`. This commit will contain the changelog and the updated version of the java modules.
77
+
- a pull request will be created on master with the changelog updates
69
78
-[ ] Merge the incoming PR created by the workflow for updating changelog on Master
70
79
-[ ] Run [`Submodules Update`](https://github.com/geosolutions-it/MapStoreExtension/actions/workflows/submodules_update.yml) on MapStoreExtension:
71
80
- Branch `YYYY.XX.xx`
@@ -82,7 +91,7 @@ This steps have to be followed always when preparing a new release.
82
91
-[ ] After "MapStore2-Stable-Build" finished, Launch [MapStore2-Stable-Deploy](http://build.geosolutionsgroup.com/view/MapStore/job/MapStore/view/MapStore%20Stable/job/MapStore2-Stable-Deploy/) to install the latest stable version on official demo.
83
92
- `branch`: `vYYYY.XX.mm` (the version tag name, e.g. v2024.01.01)
84
93
- `TAG_NAME`: `${branch}-stable` (tag of the docker hub image, previously build)
85
-
-[ ] Test the change has been applied, login on https://mapstore.geosolutionsgroup.com and verify that the layers from `gs-stable` are visible without errors (typically authentication errors that was caused by the wrong auth-key).
94
+
-[ ] Test the change has been applied, login on <https://mapstore.geosolutionsgroup.com> and verify that the layers from `gs-stable` are visible without errors (typically authentication errors that was caused by the wrong auth-key).
86
95
87
96
## Create and Publish MapStoreExtension release
88
97
@@ -116,14 +125,17 @@ When the processes are finished, the release is ready to be published on github
116
125
117
126
## Update ReadTheDocs
118
127
119
-
-[ ] create on [ReadTheDocs](https://readthedocs.org/projects/mapstore/) project the version build for `vYYYY.XX.mm` (click on "Versions" and activate the version of the tag, created when release was published)
120
-
-[ ] Update `Default version` to point the release version in the `Advanced Settings` menu of the [ReadTheDocs](https://readthedocs.org/dashboard/mapstore/advanced/)admin panel
128
+
-[ ] create on [ReadTheDocs](https://app.readthedocs.org/dashboard/mapstore/version/create/) project the version build for `vYYYY.XX.mm` (search for the tag, check the `active` toggle and click on update verson )
129
+
-[ ] Update `Default version` to point the new tag (`vYYYY.XX.mm`) in read the [ReadTheDocs Settings](https://app.readthedocs.org/dashboard/mapstore/edit/) panel and click on save.
121
130
122
131
## Finalize Release
123
132
124
133
-[ ] Run the [`Post Release`](https://github.com/geosolutions-it/MapStore2/actions/workflows/post_release.yml) workflow on github with the following parameters:
125
-
- Use workflow from branch `YYYY.XX.xx` (the release branch)
126
-
- Version of Java Packages to restore accordingly with [release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) with `-SNAPSHOT` E.g. `1.7-SNAPSHOT`
134
+
- Use workflow from branch `YYYY.XX.xx` (the release branch)
135
+
- Version of Java Packages to restore accordingly with [release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) with `-SNAPSHOT` E.g. `1.7-SNAPSHOT`
136
+
-[ ] Use the action [`Update dependencies versions`](https://github.com/geosolutions-it/MapStore2/actions/workflows/update_dependencies_versions.yml) to restore the `-SNAPSHOT` version of GeoStore, setting:
137
+
-[ ] the branch to `YYYY.XX.xx`
138
+
-[ ] the of geostore, http_proxy and mapfish-print versions accordingly with the [MapStore release calendar](https://github.com/geosolutions-it/MapStore2/wiki/MapStore-Release-Calendars) and use `-SNAPSHOT` version of geostore.
127
139
-[ ] Write to the mailing list about the current release news and the next release major changes
128
140
-[ ] Optional - prepare a PR for updating release procedure, if needed
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
130
-
asset_path: artifacts/war/mapstore.war
132
+
asset_path: artifacts/mapstore.war
131
133
asset_name: mapstore.war
132
134
asset_content_type: application/zip
133
135
- name: Upload Release binary
@@ -137,7 +139,7 @@ jobs:
137
139
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
138
140
with:
139
141
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
0 commit comments