To release IVLE, both generic source tarballs and Ubuntu packages should be published.
These instructions expect to be run on a Debian-derived system with a working IVLE installation. You also need to have your system set up with write access to Launchpad branches.
Change the two version strings in doc/conf.py and the one in ivle/__init__.py. Make sure you commit this change now.
To note down the release’s revision in the Bazaar trunk, run bzr tag -d lp:ivle VERSION.
To generate a tarball of the current state of trunk, run bzr export ivle-VERSION.tar.gz lp:ivle.
As a member of the IVLE Developers team, visit the IVLE project page. There you’ll see a graph of IVLE’s series, milestones and releases.
Clicking on the series in which this release should be created will present a list of existing milestones and releases. If a milestone for this release already exists, click “Release now”. If not, click “Create release”. Enter the release date on the following form, and confirm the creation.
To upload the release tarball for the world to see, hit “Add download file” on the release page. Give a meaningful description like “IVLE 1.0 source”, select the file, and ensure that the type is “Code Release Tarball”.
See also
An Ubuntu package is kept in the PPA for production environments. Releases should be pushed out to there if destined for production systems. The packaging is kept in a separate branch: lp:~ivle-dev/ivle/debian-packaging.
You will need to be a member of the University of Melbourne IVLE developers team, have an OpenPGP key assigned to your account, and have signed the Ubuntu Code of Conduct. See the PPA documentation linked below for instructions. You should be able to build the package on any Debian-derived operating system that uses dpkg. You also need to have an SSH key associated with your account so you can commit to the branch on Launchpad.
When performing a release, you should merge trunk into a checkout of the packaging branch. Then run dch -i to add a new Debian changelog entry. For the Debian version string, append -0ppa1 to the IVLE version (eg. 1.0-0ppa1). Make sure that you target to the correct Ubuntu series (currently hardy). Also ensure that your name and email address are set correctly at the bottom of the new entry.
Next ensure that you have a copy of the release tarball in the parent directory, named ivle_VERSION.orig.tar.gz. Once that’s there, run debuild -S -sa -i inside the checkout to build the source package and have the results placed in the parent directory.
dput ppa:unimelb-ivle/production ivle_VERSION_source.changes will now upload the package to the production PPA. You should receive an acknowledgement email from Launchpad within five minutes, at which point Launchpad will begin building binaries from the source package. You can check the build progress on the PPA detail page.
Remember to commit to and push the debian-packaging branch when done.
See also