Difference between revisions of "Release production"
| Line 4: | Line 4: | ||
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). | 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). | ||
| − | + | ||
| + | == Versions == | ||
| + | |||
| + | Make sure that versions of individual packages are properly set. | ||
| + | See [[Version management]] for details. | ||
| + | |||
== Tagging == | == Tagging == | ||
Revision as of 11:17, 30 July 2009
Contents
Testing
For Windows and Source distributions, the build process is tested automatically every night. Daily reports
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).
Versions
Make sure that versions of individual packages are properly set. See Version management for details.
Tagging
Version tags
dpsubdo dpversion t dpsubpush
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" dpsubpush
Tag list of projects and general options. Before tagging, check that the version of the project list has been properly changed !
cd admin git tag -a geopsypack-2.1.0 -m "Release Geopsy Pack 2.1.0" dppush
Publishing
On Source and Windows server:
cd windows dpfacpublish
cd sources dpfacpublish
On Mac OS X:
cd devel dpfacpublish
Updating Qt Libraries
(To edit once Qt will release 4.5.1)
