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
Any fix must be done on both 2017.02.00 and master branch
Test everything, not only the new features
Create a github release pointing to the branch 2017.02.00.
The Release name should follow be named YYYY.XX.mm where YYYY is the year, XX is the incremental number of the release for the current year (starting from 01) and the second number mm is an incremental value (starting from 00) to increment for minor releases.
Get the latest mapstore.war from the QA Jenkins build and upload it to github
Get the latest mapstore2-bin.zip from the QA Jenkins build and upload it to github
( from the job configuration page there is a link to access the job workspace to easily download the built WAR and binary package)
Write release notes with links to closed issues <-- simply linking the milestones issues page is enough. Otherwise we should produce an incremental changelog
EITHER launch Jenkins job MapStore2-Releaser OR upload the war to stable
Close the related milestone
Create a blog post
Write to the mailing list about the current release news and the next release major changes
The text was updated successfully, but these errors were encountered:
Create a branch (2017.02.00)
Create a CDN folder for the theme ( http://cdn.mapstore2.geo-solutions.it/2017.02.00/ ) <-- is it needed anymore? now we have the theme.
Commit on the new branch to change from rawgit to our CDN (index.html)
Change QA Jenkins job to build the new branch, enable the job continuous deploy
Test on QA https://qa.mapstore2.geo-solutions.it/mapstore/
Create a github release pointing to the branch 2017.02.00.
Get the latest mapstore.war from the QA Jenkins build and upload it to github
Get the latest mapstore2-bin.zip from the QA Jenkins build and upload it to github
( from the job configuration page there is a link to access the job workspace to easily download the built WAR and binary package)
Write release notes with links to closed issues <-- simply linking the milestones issues page is enough. Otherwise we should produce an incremental changelog
EITHER launch Jenkins job MapStore2-Releaser OR upload the war to stable
Close the related milestone
Create a blog post
Write to the mailing list about the current release news and the next release major changes
The text was updated successfully, but these errors were encountered: