Difference between revisions of "Release production"

From GeopsyWiki
Jump to navigation Jump to search
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Summary ==
+
== Version setup ==
=== Snapshot production ===
 
  
cd admin
+
* Commit all changes
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
+
  dpsubpush
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
 
 
 
For snapshots, tagging can be skipped (never been re-used during the past years).
 
 
 
== Testing ==
 
  
For Windows and Source distributions, the build process is tested automatically every night. [https://download.geopsy.org/releases/nextrelease.php Daily reports]
+
* Check [http://www.geopsy.org/versions versions] and eventually run version script
 +
* Update configure scripts (hard coded version)
  
For Mac OS X, the process is also automatic but it runs independently on two dedicated server. Mac OS X operating systems must run on these servers because it has not been possible to cross-compile from Linux. The server are in fact two old Mac Book Pro. There are two servers to ensure a full delivery from Leopard to Montain Lion. Unfortunately, Apple XCode provides back compatibility only down to Lion which might be frustrating for many users still working with older systems. We are trying to fight such commercial attitude.
+
  dpsubconfig -g
  
Things are even worse with El Capitan, it is no longer possible to compile for anything else than El Capitan. So we are sorry, we can deliver only El Capitan and no longer support older OS.
+
* Commit individual versions
  
== Versions ==
+
  dpsubdo dpversion c
  
Make sure that versions of individual packages are properly set.
+
If it fails, proceed to manual commit with
See [[Version management]] for details.
 
  
== Tagging ==
+
  dpsubcommit
  
To remove a tag:
+
The usual message for new versions is "Version X.Y.Z"
  
  git tag -d tag_name
+
* Tag
 
 
=== 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 ===
 
 
 
Once all tests report success, set all version numbers as explained [[Version management]].
 
 
 
Tag all sub projects
 
  
  dpsubdo git tag -a geopsypack-2.1.0 -m "Release Geopsy Pack 2.1.0"
+
* Update distribution repositories
  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 geopsypack
 +
  dpversion A B or C
 +
  dpgitconfigure
  
  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 73: 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