Difference between revisions of "Release production"

From GeopsyWiki
Jump to navigation Jump to search
 
(55 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Quick pack and testing ==
+
== Version setup ==
  
Once versions are committed but not tagged for individual packets, increase version for distribution archive. This can be done in any checked out source tree (with the appropriate branch of course)
+
* Commit all changes
  
   cd sesarray
+
   dpsubcommit
   dpversion s
+
   dpsubpush
  # Current version=2.0.3
 
  dpversion C
 
  # Current version=2.0.3
 
  # Final version=2.0.4
 
  dpversion c
 
  
On the server, start quicpack-A_B with A_B being the branch number:
+
* Check [http://www.geopsy.org/versions versions] and eventually run version script
 +
* Update configure scripts (hard coded version)
  
   cd factory
+
   dpsubconfig -g
  ./quickpack-2_0
 
  
or if you don't want to keep a terminal open:
+
* Commit individual versions
  
   cd factory
+
   dpsubdo dpversion c
  rm nohup.out
 
  nohup ./quickpack-2_0 &
 
  exit
 
  
Meanwhile you can update source trees under Mac OS X and Windows and start compilation. Make the distribution executable for these platforms (.exe or .dmg) and test it quickly (e.g. geopsy recognizes its plugins).
+
If it fails, proceed to manual commit with
  
Start automatic validation tests (takes at least 30 minutes). Absolute file path is required (to change in future?).
+
  dpsubcommit
  
  rm nohup.out
+
The usual message for new versions is "Version X.Y.Z"
  nohup ../testing/test /home/sesarray/factory/sandbox-2_0/sesarray/dist/sesarray-src-2.0.4.tar.gz &
 
  exit
 
  
The tests can be followed at [http://www.geopsy.org/testing.log testing.log].
+
* Tag
 
 
If they fail, sources can still be modified. Commit changes. If only a few packets were touched, keep the list and increase versions if necessary. If unsure, re-run complete version report. [[Manual version checks]]
 
 
 
Otherwise, proceed to [[#Pack and publish|pack and publish]]
 
 
 
== Pack and publish ==
 
 
 
Pack:
 
 
 
  cd factory
 
  rm nohup.out
 
  nohup ./pack-2_0 &
 
  exit
 
 
 
Publish (copy to ftp, insert new entry in patch generator and update files for updateIcon)
 
 
 
  cd factory
 
  rm nohup.out
 
  nohup ./publish-2_0 &
 
 
 
If everything went fine, you can tag all packets with its own version tag and with distribution archive tag
 
  
 
   dpsubdo dpversion t
 
   dpsubdo dpversion t
   dpsubdo dptag
+
   dpsubdo git tag -a geopsypack-3.3.1 -m "Release Geopsy Pack 3.3.1"
 
+
   dpsubpush -f
== Mac OS X and Windows ==
 
 
 
* Update devpro
 
 
 
  cd devtools/devpro
 
  cvs update
 
  make install
 
 
 
* Update sesarray branch
 
 
 
  cd sesarray-2.0
 
   dpsubupdate
 
  
* Change configure option to latest archive version
+
* Update distribution repositories
  
   vi admin/info
+
   cd geopsypack
   # CONFIGURE_LIB="-release -no-pch -batch -prefix $PREFIX -build-key $BUILD_KEY -distribution sesarray-2.0.4"
+
   dpversion A B or C
 +
  dpgitconfigure
  
* Configure and make
+
* Start compilation servers manually or wait for night build
  
  dpsubconfig -f
+
== Release Notes ==
  dpsubmake
 
  
For Mac:
+
Release notes are built from commit comments.
  
  cd sesarray
+
dpsubreleasenotes 2.2.1 2.3.0
  dppackmac
 
  
For Windows
+
Eventually edit the final file before its publication:
  
  cd sesarray
+
scp release_notes-2.3.0 geopsy.org:/var/www/geopsy/htdocs/release_notes
  dppackwin
 
  
== Updating Qt ==
+
== Publishing ==
  
=== Mac OS X ===
+
* Connect on geopsy.org
 +
* Run in build directory
  
Usually, to avoid double Qt libraries plugins must be turned off by renaming ''/usr/local/Trolltech/Qt/plugins'' into ''plugins-off''. When upgrading to new Qt release, you must rename the new ''plugins'' directory and remove the old one. dppack is fetching plugins in ''plugins-off'' directory.
+
  ./publish src 3.4
  
=== Windows ===
+
and
  
Manually copy Qt dll and 'plugins' directory to ''/c/usr/sesarray-2.0/bin''. Do this for all active branches.
+
  ./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