Difference between revisions of "Release production"

From GeopsyWiki
Jump to navigation Jump to search
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Testing or Stable release production ==
+
== Version setup ==
  
 
* Commit all changes
 
* Commit all changes
Line 6: Line 6:
 
   dpsubpush
 
   dpsubpush
  
* Check versions and eventually run version script
+
* Check [http://www.geopsy.org/versions versions] and eventually run version script
* Set geopsy pack next version
 
 
 
  cd admin
 
  dpversion A B or C
 
  dpversion c
 
  git tag -a geopsypack-3.1.1 -m "Release Geopsy Pack 3.1.1"
 
  dppush
 
 
 
 
* Update configure scripts (hard coded version)
 
* Update configure scripts (hard coded version)
  
   dpsubconfig -g -f
+
   dpsubconfig -g
  
* Commit and tag
+
* Commit individual versions
  
 
   dpsubdo dpversion c
 
   dpsubdo dpversion c
  dpsubdo dpversion t
 
  dpsubdo git tag -a geopsypack-3.1.1 -m "Release Geopsy Pack 3.1.1"
 
  dpsubpush -f
 
 
 
== Devel snapshot production ==
 
  
cd admin
+
If it fails, proceed to manual commit with
dpversion S
 
dpversion c
 
[git tag -a geopsypack-2.1.0-snapshot-20090730 \
 
          -m "Release Geopsy Pack 2.1.0-snapshot-20090730"]
 
dppush
 
  
dpsubcommit
+
  dpsubcommit
dpsubdo dpversion S
 
dpsubconfig -g -f
 
dpsubdo dpversion c
 
[dpsubdo dpversion t]
 
[dpsubdo git tag -a geopsypack-2.1.0-snapshot-20090730 \
 
                  -m "Release Geopsy Pack 2.1.0-snapshot-20090730"]
 
dpsubpush -f
 
  
For snapshots, tagging can be skipped (never been re-used during the past years).
+
The usual message for new versions is "Version X.Y.Z"
  
== Testing ==
+
* Tag
 
 
The build process is tested automatically every day for Linux, Windows and Mac OS distributions. [http://www.geopsy.org/download/nextrelease.php Daily reports]
 
 
 
An automatic testbench would be helpful.
 
 
 
== Versions ==
 
 
 
Make sure that versions of individual packages are properly set.
 
See [[Version management]] for details.
 
 
 
== Tagging ==
 
 
 
To remove a tag:
 
 
 
  git tag -d tag_name
 
 
 
=== Version tags ===
 
 
 
Automatic version statistics do take into account only changes of .cpp and .h files. All other modification must be checked manually.
 
  
 
   dpsubdo dpversion t
 
   dpsubdo dpversion t
   dpsubpush
+
  dpsubdo git tag -a geopsypack-3.3.1 -m "Release Geopsy Pack 3.3.1"
 +
   dpsubpush -f
  
=== Geopsy Pack tags ===
+
* Update distribution repositories
  
Once all tests report success, set all version numbers as explained [[Version management]].
+
   cd geopsypack
 
+
   dpversion A B or C
Tag all sub projects
+
  dpgitconfigure
 
 
   dpsubdo git tag -a geopsypack-2.1.0 -m "Release Geopsy Pack 2.1.0"
 
   dpsubpush -f
 
 
 
Tag list of projects and general options. Before tagging, check that the version of the project list has been [[Version_management#Version_of_project_list|properly changed]] !
 
  
  cd admin
+
* Start compilation servers manually or wait for night build
  git tag -a geopsypack-2.1.0 -m "Release Geopsy Pack 2.1.0"
 
  dppush
 
  
 
== Release Notes ==
 
== Release Notes ==
Line 97: Line 47:
 
== Publishing ==
 
== Publishing ==
  
Through web interface after an administrator login in "status"
+
* Connect on geopsy.org
 +
* Run in build directory
 +
 
 +
  ./publish src 3.4
 +
 
 +
and
 +
 
 +
  ./publish win64 3.4

Latest revision as of 15:34, 3 May 2021

Version setup

  • Commit all changes
 dpsubcommit
 dpsubpush
  • Check versions and eventually run version script
  • Update configure scripts (hard coded version)
 dpsubconfig -g
  • Commit individual versions
 dpsubdo dpversion c

If it fails, proceed to manual commit with

 dpsubcommit

The usual message for new versions is "Version X.Y.Z"

  • Tag
 dpsubdo dpversion t
 dpsubdo git tag -a geopsypack-3.3.1 -m "Release Geopsy Pack 3.3.1"
 dpsubpush -f
  • Update distribution repositories
 cd geopsypack
 dpversion A B or C
 dpgitconfigure
  • Start compilation servers manually or wait for night build

Release Notes

Release notes are built from commit comments.

dpsubreleasenotes 2.2.1 2.3.0

Eventually edit the final file before its publication:

scp release_notes-2.3.0 geopsy.org:/var/www/geopsy/htdocs/release_notes

Publishing

  • Connect on geopsy.org
  • Run in build directory
 ./publish src 3.4

and

  ./publish win64 3.4