22
22
To release IVLE, both generic source tarballs and Ubuntu packages should
25
Generating a source tarball
26
===========================
25
These instructions expect to be run on a Debian-derived system with a
26
working IVLE installation. You also need to have your system set up with
27
write access to Launchpad branches.
30
Update the internal version strings
31
===================================
33
Change the two version strings in ``doc/conf.py`` and the one in
34
``ivle/__init__.py``. Make sure you commit this change now.
37
Tag the release in Bazaar
38
=========================
40
To note down the release's revision in the Bazaar trunk, run ``bzr tag
44
Generate a source tarball
45
=========================
28
47
To generate a tarball of the current state of trunk, run ``bzr export
29
48
ivle-VERSION.tar.gz lp:ivle``.
32
Releasing it on Launchpad
33
=========================
51
Release it on Launchpad
52
=======================
35
54
As a member of the `IVLE Developers <https://launchpad.net/~ivle-dev>`_ team,
36
55
visit the `IVLE project page <https://launchpad.net/ivle>`_. There you'll see
56
Updating the Ubuntu package
57
===========================
75
Publish an Ubuntu package
76
=========================
59
78
An Ubuntu package is kept in the `PPA for production environments
60
79
<https://launchpad.net/~unimelb-ivle/+archive/production>`_. Releases should
67
86
your account, and have signed the Ubuntu Code of Conduct. See the PPA
68
87
documentation linked below for instructions. You should be able to build
69
88
the package on any Debian-derived operating system that uses ``dpkg``.
89
You also need to have an SSH key `associated with your account
90
<https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair>`_ so you can
91
commit to the branch on Launchpad.
71
93
When performing a release, you should merge trunk into a checkout of the
72
94
packaging branch. Then run ``dch -i`` to add a new Debian changelog entry.
73
95
For the Debian version string, append ``-0ppa1`` to the IVLE version (eg.
74
``1.0-0ppa1``). Make sure that you target to the correct Ubuntu series (
75
currently ``hardy``). Also ensure that your name and email address are set
96
``1.0-0ppa1``). Make sure that you target to the correct Ubuntu series
97
(currently ``hardy``). Also ensure that your name and email address are set
76
98
correctly at the bottom of the new entry.
78
100
Next ensure that you have a copy of the release tarball in the parent
79
101
directory, named ``ivle_VERSION.orig.tar.gz``. Once that's there, run
80
``debuild -S -sa -i`` to build the source package in the parent directory.
102
``debuild -S -sa -i`` inside the checkout to build the source package and
103
have the results placed in the parent directory.
82
105
``dput ppa:unimelb-ivle/production ivle_VERSION_source.changes`` will now
83
106
upload the package to the production PPA. You should receive an acknowledgement
84
107
email from Launchpad within five minutes, at which point Launchpad will begin
85
108
building binaries from the source package. You can check the build progress
86
109
on the `PPA detail page
87
<https://~unimelb-ivle/+archive/production/+packages>`_.
110
<https://launchpad.net/~unimelb-ivle/+archive/production/+packages>`_.
89
112
Remember to commit to and push the ``debian-packaging`` branch when done.
added
removed
doc/dev/releases.rst
