source:
branches/PublicaMundi_David-devel/docs/contribute/release.rst
@
938
| Last change on this file since 938 was 702, checked in by djay, 9 years ago | |
|---|---|
| File size: 3.4 KB | |
Release Procedure
The ZOO-Project release procedure is commonly defined by the following rules:
Any of the :ref:`zoo_developers` can ask for a release by asking the :ref:`zoo_psc` and pointing a release manager. This last will then vote for accepting both the manager and the release procedure to happen.
If not already created, create a wiki page (like this this one using this scheme: Release/M.m.r/Notes), summarizing changes from the previous release (extracted from the revision log).
That file should include new features, changed features, and deprecated features if any. Changes to the official documentation should be specifically noted along with other items that will cause breaking changes during upgrades.
Read the documentation and remove outdated parts.
Create release candidate as .zip and .tar.bz2 then add them on this page (by editing this wiki page)
Cut a release candidate once you think that everything is in order. Announce the release candidate for review for at least 1 week. In this period of time, it is also appropriate for you to deploy in production since you are asserting that it is stable and (significant) bug free. Publish a specific revision with this.
If significant bugs are reported, fix and cut a new release candidate. If no major bugs, then announce that the release candidate has officially been promoted to the official release (if you want, you can do this with a motion and support of the PSC).
Ensure that release exactly matches something in SVN. Tag and branch appropriately.
Update documentation as needed.
Announce on various email list and other locations (news_item@osgeo.org, SlashGeo, etc)
Creating an Official Release
Release versions lead to an update in documentation and standard tarballs. This is to help future administrators repeatably create releases.
- Double check that the pages from the ZOO-Project.org web site match the current version.
- Double check that the latest build file matches the current revisions number.
- If this is a new major release create a branch and a tag.
cd zoo-project-svn/ svn cp trunk branches/branch-1.6 svn cp trunk tags/rel-1.6.0
- If this is a major or minor relase, create a tag.
svn cp branches/branch-1.6 tags/rel-1.6.1
- Commit the tags or branches with the version numbers.
svn commit -m 'Created branch/tags for the X.Y.Z release'
- Create version archives
export VERSION=2.6.0
cd zoo-propject-svn
cp -r trunk zoo-project-$VERSION
cd zoo-project-$VERSION
rm -rf $(find ./ -name ".svn")
cd zoo-project/zoo-kernel
autoconf
cd ../../..
# Remove documentation from the archive
rm -rf ./zoo-project-$VERSION/docs
tar -cvjf ./zoo-project-$VERSION.tar.bz2 ./zoo-project-$VERSION
zip -r ./zoo-project-$VERSION.zip ./zoo-project-$VERSION
scp -P 1046 ./zoo-project-$VERSION.{zip,tar.bz2} zoo-project.org:/var/www/localhost/htdocs/dl/
- Update the Downloads page to add the latest release (by editing this wiki page).
