1
.. IVLE - Informatics Virtual Learning Environment
2
Copyright (C) 2007-2009 The University of Melbourne
4
.. This program is free software; you can redistribute it and/or modify
5
it under the terms of the GNU General Public License as published by
6
the Free Software Foundation; either version 2 of the License, or
7
(at your option) any later version.
9
.. This program is distributed in the hope that it will be useful,
10
but WITHOUT ANY WARRANTY; without even the implied warranty of
11
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12
GNU General Public License for more details.
14
.. You should have received a copy of the GNU General Public License
15
along with this program; if not, write to the Free Software
16
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
22
To release IVLE, both generic source tarballs and Ubuntu packages should
26
Tag the release in Bazaar
27
=========================
29
To note down the release's revision in the Bazaar trunk, run ``bzr tag
33
Generating a source tarball
34
===========================
36
To generate a tarball of the current state of trunk, run ``bzr export
37
ivle-VERSION.tar.gz lp:ivle``.
40
Releasing it on Launchpad
41
=========================
43
As a member of the `IVLE Developers <https://launchpad.net/~ivle-dev>`_ team,
44
visit the `IVLE project page <https://launchpad.net/ivle>`_. There you'll see
45
a graph of IVLE's series, milestones and releases.
47
Clicking on the series in which this release should be created will present
48
a list of existing milestones and releases. If a milestone for this release
49
already exists, click "Release now". If not, click "Create release". Enter
50
the release date on the following form, and confirm the creation.
52
To upload the release tarball for the world to see, hit "Add download file" on
53
the release page. Give a meaningful description like "IVLE 1.0 source", select
54
the file, and ensure that the type is "Code Release Tarball".
59
`Launchpad release documentation <https://help.launchpad.net/Projects/SeriesMilestonesReleases>`_
60
All you could ever want to know about Launchpad's series, milestones and
64
Updating the Ubuntu package
65
===========================
67
An Ubuntu package is kept in the `PPA for production environments
68
<https://launchpad.net/~unimelb-ivle/+archive/production>`_. Releases should
69
be pushed out to there if destined for production systems. The packaging is
70
kept in a separate branch: `lp:~ivle-dev/ivle/debian-packaging
71
<https://code.launchpad.net/~ivle-dev/ivle/debian-packaging>`_.
73
You will need to be a member of the `University of Melbourne IVLE developers
74
<https://launchpad.net/~unimelb-ivle>`_ team, have an OpenPGP key assigned to
75
your account, and have signed the Ubuntu Code of Conduct. See the PPA
76
documentation linked below for instructions. You should be able to build
77
the package on any Debian-derived operating system that uses ``dpkg``.
78
You also need to have an SSH key `associated with your account
79
<https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair>`_ so you can
80
commit to the branch on Launchpad.
82
When performing a release, you should merge trunk into a checkout of the
83
packaging branch. Then run ``dch -i`` to add a new Debian changelog entry.
84
For the Debian version string, append ``-0ppa1`` to the IVLE version (eg.
85
``1.0-0ppa1``). Make sure that you target to the correct Ubuntu series
86
(currently ``hardy``). Also ensure that your name and email address are set
87
correctly at the bottom of the new entry.
89
Next ensure that you have a copy of the release tarball in the parent
90
directory, named ``ivle_VERSION.orig.tar.gz``. Once that's there, run
91
``debuild -S -sa -i`` to build the source package and have the results placed
92
in the parent directory.
94
``dput ppa:unimelb-ivle/production ivle_VERSION_source.changes`` will now
95
upload the package to the production PPA. You should receive an acknowledgement
96
email from Launchpad within five minutes, at which point Launchpad will begin
97
building binaries from the source package. You can check the build progress
98
on the `PPA detail page
99
<https://launchpad.net/~unimelb-ivle/+archive/production/+packages>`_.
101
Remember to commit to and push the ``debian-packaging`` branch when done.
105
`Launchpad PPA documentation <https://help.launchpad.net/Packaging/PPA>`_
106
All you could ever want to know about using Launchpad's PPA
109
`Ubuntu Packaging Guide <https://wiki.ubuntu.com/PackagingGuide/Basic>`_
110
All you could ever want to know about Ubuntu packaging.