Difference between revisions of "Release production"

From GeopsyWiki
Jump to navigation Jump to search
 
(23 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Summary ==
+
== Version setup ==
=== Snapshot production ===
 
  
dpsubcommit -gui
+
* Commit all changes
dpsubdo dpversion S
 
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
 
cd admin
 
dpversion S
 
dpversion c
 
[git tag -a geopsypack-2.1.0-snapshot-20090730 -m "Release Geopsy Pack 2.1.0-snapshot-20090730"]
 
dppush
 
  
For snapshots, tagging can be skipped (never been re-used during the past years).
+
  dpsubcommit
 +
  dpsubpush
 +
 
 +
* Check [http://www.geopsy.org/versions versions] and eventually run version script
 +
* Update configure scripts (hard coded version)
  
== Testing ==
+
  dpsubconfig -g
  
For Windows and Source distributions, the build process is tested automatically every night. [http://www.geopsy.org/nextrelease.php Daily reports]
+
* Commit individual versions
  
For Mac OS X, the process is also automatic but it does not run independently on a dedicated server. Instead, it is run manually (buying and installing a dedicated server, e.g. a Mac Mini would be enough, would rather help).
+
  dpsubdo dpversion c
  
== Versions ==
+
If it fails, proceed to manual commit with
  
Make sure that versions of individual packages are properly set.
+
  dpsubcommit
See [[Version management]] for details.
 
  
== Tagging ==
+
The usual message for new versions is "Version X.Y.Z"
  
=== Version tags ===
+
* Tag
  
 
   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 61: Line 47:
 
== Publishing ==
 
== Publishing ==
  
Through web interface after an administrator login in "status"
+
* Connect on geopsy.org
 
+
* Run in build directory
== Updating Qt Libraries ==
 
 
 
Qt updates take place only when required for fixing bugs related to Qt. Else, we follow Ubuntu integration of Qt. Current status is available at [http://packages.ubuntu.com/search?keywords=qt4-qmake&searchon=names&section=all http://packages.ubuntu.com].
 
 
 
New Qt release should compile and be tested successfully under development environment before switching to a new Qt release.
 
 
 
=== Source ===
 
 
 
cd /build/qt
 
cp build-4.6 build-4.7
 
 
 
Change Qt version number in script header. Download Qt archive:
 
  
wget ftp://ftp.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.7.3.tar.gz
+
  ./publish src 3.4
  
Start compilation:
+
and
  
nohup ./build-4.7
+
  ./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