These instructions are the guidelines for anyone making a Pootle commit.
We need to check and document these if needed:
We work from a clean checkout to esnure that everything you are adding to the build is what is in VC and doesn’t contain any of your uncommitted changes. It also ensure that someone else could relicate your process.
git clone git@github.com:translate/pootle.git pootle-release
The release notes will be used in these places:
We create our release notes in reStructured Text, since we use that elsewhere and since it can be rendered well in some of our key sites.
First we need to create a log of changes in Pootle:
git diff N-1 HEAD > docs/release/$version.rst
Edit this new file. You can use the commits as a guide to build up the release notes. You should remove all log messages before the release.
Note
Since the release notes will be used in places that allow linking we use links within the notes. These should link back to products websites (Virtaal, Pootle, etc), references to Translate and possibly bug numbers, etc.
Read for grammar and spelling errors.
Note
When writing the notes please remember:
Update the version number in:
In __version__.py, bump the build number if anybody used the toolkit with the previous number, and there have been any changes to code touching stats or quality checks. An increased build number will force a toolkit user, like Pootle, to regenerate the stats and checks.
For conf.py change version and release
Note
FIXME - We might want to automate the version and release info so that we can update it in one place.
The version string should follow the pattern:
$MAJOR-$MINOR-$MICRO[-$EXTRA]
E.g.
1.10.0
0.9.1-rc1
$EXTRA is optional but all the three others are required. The first release of a $MINOR version will always have a $MICRO of .0. So 1.10.0 and never just 1.10.
Update the translations from the Pootle server
Download all translations:
# On pootle.locamotion.org
./manage.py sync_stores --project=pootle
# On your computer
scp -rp $user@pootle.locamotion.org/$location pootle/locales
Update pootle/locale/LINGUAS to list the languages we would like to ship. While we package all PO files, this is an indication of which ones we want packagers to use. The requirements is roughly 100% translated with no obvious variable errors.
.. code-block:: bash
$ make mo # Build all LINGUAS enabled languages
Building is the first step to testing that things work. From your clean checkout run:
make mo-all # if we are shipping an pre-release
make build
This will create a tarball in dist/ which you can use for further testing.
Note
We use a clean checkout just to make sure that no inadvertant changes make it into the release.
The easiest way to test is in a virtualenv. You can install the new toolkit using:
pip install path/to/dist/Pootle-$version.tar.bz2
This will allow you test installation of the software.
You can then proceed with other tests such as checking:
You should only tag once you are happy with your release as there are some things that we can’t undo.
git tag -a 2.5.0 -m "Tag version 2.5.0"
git push --tags
If this is the final release then there should be a stable branch e.g. stable/2.5.0, so create one if it does not already exist.
Publish the package on the Python Package Index (PyPI)
Note
You need a username and password on https://pypi.python.org and have rights to the project before you can proceed with this step.
These can be stored in $HOME/.pypirc and will contain your username and password. A first run of ./setup.py register will create such a file. It will also actually publish the meta-data so only do it when you are actually ready.
Review the meta data. This is stored in setup.py, use ./setup.py --help to se some options to display meta-data. The actual long description is taken from /README.rst.
To test before publishing run:
make test-publish-pypi
Then to actually publish:
make publish-pypi
Publishing files to the Translate Sourceforge project.
Note
You need to have release permissions on sourceforge to perform this step.
You will need:
We need a tagged release or branch before we can do this. The docs are published on Read The Docs.
Use the admin pages to flag a version that should be published. When we have branched the stable release we use the branch rather then the tag i.e. stable-2.5.0 rather than 2.5.0 as that allows any fixes of documentation for the 2.5.0 release to be immediately available.
Change all references to docs in the Pootle code to point to the branched version as apposed to the latest version.
We use github pages for the website. First we need to checkout the pages:
git checkout gh-pages
Note
FIXME it would be great if gh-pages accepted .rst, maybe it can if we prerender just that page?
If you have created a staged release folder, then unstage it now.
Let people know that there is a new version:
Some possible cleanup tasks: