Introduction
The Tryton Release process is inspired by the OpenBSD Release Process. To get a conception of the process please have a look at a video of The OpenBSD Release Process at AsiaBSDCon 2009 The next release date is chosen after a release and published at Tryton's calendar
What is released?
- Every part of Tryton, the user needs to install and run the complete application.
- Development and build-for-release specific parts are not released, they are always current in the development tree.
Maintenance
Major releases are maintained for at least 2.5 years which means there will be minor releases for this series during this period.
Version number of Tryton releases
The Tryton version number is made of thee parts like the following example:
Tryton Version 2.3.5
Major release
The first and second number are major version numbers. These general version numbers ...
- ... are used to indicate a major step in the evolution of Tryton;
- ... are published twice per year;
- ... can change parts of the database structure;
- ... could need manual steps for database upgrade;
Minor release
The third number is the minor version number of Tryton. Releases changing this number...
- ... are published for fix bugs;
- ... don't change the database structure;
- ... don't need a database upgrade;
- ... are considered as unproblematic for update;
Development state
The second number indicates development state:
- even number and null: Release version
- odd number: Development version
Major release preparation
The development is frozen about 1 month before the scheduled date.
"freezing" is handled by maintainers discipline.
During freezing:
- Leaders check their modules (and documentation) and fix reported issues.
- Translation teams update the translation of each repositories.
- Everybody test and report issues until release.
Release process
- For major release, update the major version number.
- Prepare the CHANGELOG file with the release date.
- Run update_copyright.py script.
- Tag the mercurial repository with the release number.
- Create the source distribution (tarball) with:
# python setup.py register sdist upload
Upload to http://downloads.tryton.org/ For major release, create a new named branch at the tag revision. Increase the version number For major release, increase the version number of the development repository to the next odd number.