Skip to content
This repository was archived by the owner on May 6, 2021. It is now read-only.

MapStore Release Procedure

Tobia edited this page Feb 19, 2014 · 6 revisions
  1. Open the issue inside the related milestone in github

  2. Create a new branch 1.N.x

  3. In 1.N.x create Tag 1.N_branch

    git tag -a 1.N_branch -m "Prepare 1.N release" git push origin 1.N.x --tags

  4. In 1.N.x change the version reference for the other application (i.e ServiceBox, http_proxy etc...) ONLY IF necessary

  5. In 1.N.x make a check build and a check tour of the main component:

     - MapManager
     - WMSGetFeatureInfo tools
     - MarkerEditor
     - Metauada explorer
     - Import Export
     - Print plugin 
     - BBOXQueryForm
     - PrintSnapshot
    

Then should be tested also:

	- MapStore Binary    (using 'ant release' and 'ant gnrelease')
	- MapStore Installer (https://github.com/geosolutions-it/mapstore/wiki/Windows-Installer)
  1. In 1.N.x make a 'mvn deploy' (THIS NOT FOR MAPSTORE but only for maven applications: GeoStore, ServiceBox, Http_Proxy etc...)

  2. In 1.N.x do commit&push(-m "Prepare for next 1.N release iteration")

  3. In 1.N.x create a Tag v1.N and push it:

     git tag -a v1.N -m "Final 1.N release"
     git push origin 1.N.x --tags
    
  4. In 1.N.x change the version reference with the olds one and then make commit&push

             (-m "Revert the project to the 1.N-SNAPSHOT version")
    
  5. In master upgrade the project version 1.(N+1)-SNAPSHOT and then do commit&push

            (-m "Update the project to the 1.(N+1)-SNAPSHOT version")
    
  6. In master make a 'mvn deploy' for the new SNAPSHOT (THIS NOT FOR MAPSTORE but only for maven applications: GeoStore, ServiceBox, Http_Proxy etc...)

  7. Close the opened issue on GitHub

Clone this wiki locally