This page is divided in four sections. The first one lists the tasks that must be performed before creating a package. The second section includes a list of tasks to get a valid package. The third one to get the package published and the release announced. The last one lists and suggests some possible cleanup tasks to be done after releasing.
Note
Please note that this is not a complete list of tasks. Please feel free to improve it.
Before starting the release process it is necessary to perform some previous tasks.
We need to give localizers enough time to localize Pootle. They need time to do the actual translation and to feedback on any errors that they might encounter.
First upload the new translations:
Create the new templates:
$ git clone git@github.com:translate/pootle.git pootle-translations
$ cd pootle-translations
$ make pot
Upload the templates to Pootle for translation.
Update current translations against templates either on Pootle or in code and commits these updated files to Git.
Announce the new translations on the following channels:
A string freeze would normally run between an RC and a final version. We want to give a string freeze at least 2-4 weeks before a release. They must be announced, explicitly stating the duration, on the translate-announce@lists.sourceforge.net and the translate-pootle@lists.sourceforge.net mailing lists.
Note
If we do have a string freeze break then announce it to people. The string freeze breaks usually are only allowed to fix mistakes on the translatable strings.
The first steps are to create and validate a package for the next release.
We work from a clean checkout to ensure that everything you are adding to the build is what is in the repository and doesn’t contain any of your uncommitted changes. It also ensures that someone else could replicate your process.
$ git clone git@github.com:translate/pootle.git pootle-release
$ cd pootle-release
$ git submodule update --init
Make sure the versions listed in docs/server/installation.rst
match
those in requirements/base.txt
.
Update the minimum version number for the requirements in:
requirements/
pootle/depcheck.py
Update the requirements files:
$ make requirements-pinned.txt
Note
This creates the following files:
requirements-pinned.txt
- the maximum available version when
we released. Chances are we’ve tested with these and they are good.
Using this would prevent a person from installing something newer but
untested.The roadmap file needs to be updated. Remove things that are part of this release. Adjust any version numbering if for example we’re moving to Django 1.6 we need to change the proposed release numbers.
Look at the actual roadmap commitments and change if needed. These will remain during the lifetime of this version so it is good to adjust them before we branch.
Update any copyright dates in docs/conf.py:copyright
and anywhere else
that needs fixing.
$ git grep 2013 # Should pick up anything that should be examined
Update the translations from the Pootle server
Download all translations
$ make get-translations
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 requirement is roughly 80% translated with no
obvious variable errors. Languages with a small userbase can be included.
$ make linguas
Check the output and make any adjustments such as adding back languages that don’t quite make the target but you wish to ship.
Build translations to check for errors:
$ make mo # Build all LINGUAS enabled languages
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, which is done generically like this:
$ git log $previous_version..HEAD > docs/release/$version.rst
Or a more specific example:
$ git log 2.5.0..HEAD > docs/releases/2.5.1.rst
Edit this 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:
We create a list of contributors using this command:
$ git log 2.5.0..HEAD --format='%aN, ' | awk '{arr[$0]++} END{for (i in arr){print arr[i], i;}}' | sort -rn | cut -d\ -f2-
Update the version number in:
pootle/__version__.py
docs/conf.py
In pootle/__version__.py
, bump the build number if anybody used Pootle
with the previous number, and there have been any changes to code touching
stats or quality checks.
For docs/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
2.6.0
and never just 2.6
.
Building is the first step to testing that things work. From your clean checkout run:
$ mkvirtualenv build-pootle-release
(build-pootle-release)$ pip install -r requirements/build.txt
(build-pootle-release)$ make mo-all # If we are shipping an RC
(build-pootle-release)$ make build
(build-pootle-release)$ deactivate
$ rmvirtualenv build-pootle-release
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 test the installation of the new release using:
$ mkvirtualenv test-pootle-release
(test-pootle-release)$ pip install dist/Pootle-$version.tar.bz2
(test-pootle-release)$ pip install MySQL-python
(test-pootle-release)$ pootle init
You can then proceed with other tests such as checking:
Documentation is available in the package
MySQL upgrade check:
Download a database dump from Pootle Test Data repository
Create a blank database on MySQL:
mysql -u $db_user -p$db_password -e 'CREATE DATABASE `test-mysql-pootle` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;'
Import the database dump into the MySQL database:
mysql -u $db_user -p$db_password test-mysql-pootle < $db_dump_file
Run the following:
(test-pootle-release)$ pootle setup
(test-pootle-release)$ pootle start
(test-pootle-release)$ # Browse to localhost:8000
Drop the MySQL database you have created:
mysql -u $db_user -p$db_password -e 'DROP DATABASE `test-mysql-pootle`;'
Check that the instructions in the Installation guide are correct
Check that the instructions in the Upgrade guide are correct
Check that the instructions in the Hacking guide are correct
Meta information about the package is correct. This is stored in
setup.py
, to see some options to display meta-data use:
$ ./setup.py --help
Now you can try some options like:
$ ./setup.py --name
$ ./setup.py --version
$ ./setup.py --author
$ ./setup.py --author-email
$ ./setup.py --url
$ ./setup.py --license
$ ./setup.py --description
$ ./setup.py --long-description
$ ./setup.py --classifiers
The actual long description is taken from /README.rst
.
Finally clean your test environment:
(test-pootle-release)$ deactivate
$ rmvirtualenv test-pootle-release
Once we have a valid package it is necessary to publish it and announce the release.
You should only tag once you are happy with your release as there are some
things that we can’t undo. You can safely branch for a stable/
branch
before you tag.
$ git checkout -b stable/2.6.0
$ git push origin stable/2.6.0
$ git tag -a 2.6.0 -m "Tag version 2.6.0"
$ git push --tags
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.
Note
You need a username and password on Python Package Index (PyPI) 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 file. It will also actually publish the meta-data so only do it when you are actually ready.
Run the following to publish the package on PyPI:
$ make publish-pypi
You will need:
Do the following to create the release:
We use github pages for the website. First we need to checkout the pages:
$ git checkout gh-pages
_posts/
add a new release posting. Use the same text used for the
Github release description,
including the link to the full release notes.$version
as needed. See download.html
,
_config.yml
and git grep $old_releaseNote
FIXME it would be great if gh-pages accepted .rst, maybe it can if we prerender just that page?
Let people know that there is a new version:
Announce on mailing lists using plain text emails using the same text (adjusting what needs to be adjusted) used for the Github release description:
Adjust the #pootle channel notice. Use /topic [new topic]
to change the
topic. It is easier if you copy the previous topic and adjust it.
Note
You might need to identify yourself by using
/msg nickserv identify [password]
so the IRC server knows you in
order to check if you have enough permissions.
Email important users
Tweet about it
Update Pootle’s Wikipedia page
These are tasks not directly related to the releasing, but that are nevertheless completely necessary.
If this new release is a stable one, bump the version in master
to
{N+1}-alpha1
. The places to be changed are the same ones listed in
Up version numbers. This prevents anyone
using master
being confused with a stable release and we can easily check
if they are using master
or stable
.
After updating the release notes for the about to be released version, it is
necessary to add new release notes for the next release, tagged as dev
.
Some possible cleanup tasks:
pootle-release
checkout.master
.$version
docs rather then latest
?