Difference between revisions of "Release production"

From GeopsyWiki
Jump to navigation Jump to search
 
(5 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
+
* Update configure scripts (hard coded version)
  
   cd admin
+
   dpsubconfig -g
  dpversion A B or C
+
 
   dpversion c
+
* Commit individual versions
  git tag -a geopsypack-3.1.1 -m "Release Geopsy Pack 3.1.1"
+
 
  dppush
+
   dpsubdo dpversion c
 +
 
 +
If it fails, proceed to manual commit with
  
* Update configure scripts (hard coded version)
+
  dpsubcommit
  
  dpsubconfig -g -f
+
The usual message for new versions is "Version X.Y.Z"
  
* Commit and tag
+
* Tag
  
  dpsubdo dpversion c
 
 
   dpsubdo dpversion t
 
   dpsubdo dpversion t
   dpsubdo git tag -a geopsypack-3.1.1 -m "Release Geopsy Pack 3.1.1"
+
   dpsubdo git tag -a geopsypack-3.3.1 -m "Release Geopsy Pack 3.3.1"
 
   dpsubpush -f
 
   dpsubpush -f
  
* Start compilation servers manually or wait for night build
+
* Update distribution repositories
  
== Devel snapshot production ==
+
  cd geopsypack
 +
  dpversion A B or C
 +
  dpgitconfigure
  
cd admin
+
* Start compilation servers manually or wait for night build
dpversion S
 
dpversion c
 
[git tag -a geopsypack-2.1.0-snapshot-20090730 \
 
          -m "Release Geopsy Pack 2.1.0-snapshot-20090730"]
 
dppush
 
 
 
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).
 
  
 
== Release Notes ==
 
== Release Notes ==
Line 60: Line 47:
 
== Publishing ==
 
== Publishing ==
  
If build process successful, files are available in
+
* Connect on geopsy.org
 
+
* Run in build directory
  /geopsy/build/candidates
 
 
 
Go to
 
 
 
  /geopsy/build/archives
 
  
Run
+
  ./publish src 3.4
  
  ./generate win64 testing 3.1.1 <DATE>
+
and
  
Follow instruction at the end to publish the files.
+
  ./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