Merge lp:~dholbach/ubuntu-packaging-guide/1017984 into lp:ubuntu-packaging-guide

Proposed by Daniel Holbach
Status: Merged
Merged at revision: 118
Proposed branch: lp:~dholbach/ubuntu-packaging-guide/1017984
Merge into: lp:ubuntu-packaging-guide
Diff against target: 60 lines (+45/-0)
2 files modified
ubuntu-packaging-guide/backports.rst (+44/-0)
ubuntu-packaging-guide/index.rst (+1/-0)
To merge this branch: bzr merge lp:~dholbach/ubuntu-packaging-guide/1017984
Reviewer Review Type Date Requested Status
Andrew Starr-Bochicchio Approve
Review via email:

Description of the change

Refer to backports process in packaging guide.

To post a comment you must log in.
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

I went ahead and landed this, but it would probably be nice to include a link to and maybe a discussion of the `backportpackage` command from ubuntu-dev-tools.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== added file 'ubuntu-packaging-guide/backports.rst'
2--- ubuntu-packaging-guide/backports.rst 1970-01-01 00:00:00 +0000
3+++ ubuntu-packaging-guide/backports.rst 2012-06-26 16:03:20 +0000
4@@ -0,0 +1,44 @@
6+Backporting software updates
9+Sometimes you might want to make new functionality available in a stable
10+release which is not connected to a critical bug fix. For these scenarios
11+you have two options: either you `upload to a PPA
12+<>`_ or prepare a backport.
15+Personal Package Archive (PPA)
18+Using a PPA has a number of benefits. It is fairly straight-forward, you
19+don't need approval of anyone, but the downside of it is that your users will
20+have to manually enable it. It is a non-standard software source.
22+The `PPA documentation on Launchpad`_ is fairly comprehensive and should get
23+you up and running in no time.
25+.. _PPA documentation on Launchpad:
28+Official Ubuntu Backports
31+The Backports Project is a means to provide new features to users. Because of
32+the inherent stability risks in backporting packages, users do not get
33+backported packages without some explicit action on their part. This
34+generally makes backports an inappropriate avenue for fixing bugs. If a
35+package in an Ubuntu release has a bug, it should be fixed either through the
36+:doc:`Security Update or the Stable Release Update
37+process<./security-and-stable-release-updates>`, as appropriate.
39+Once you determined you want a package to be backported to a stable release,
40+you will need to test-build and test it on the given stable release.
41+``pbuilder-dist`` (in the ``ubuntu-dev-tools`` package) is a very handy tool
42+to do this easily.
44+To report the backport request and get it processed by the Backporters team,
45+you can use the ``requestbackport`` tool (also in the ``ubuntu-dev-tools``
46+package). It will determine the intermediate releases that package needs to
47+be backported to, list all reverse-dependencies, and file the backporting
48+request. Also will it include a testing checklist in the bug.
50=== modified file 'ubuntu-packaging-guide/index.rst'
51--- ubuntu-packaging-guide/index.rst 2012-05-09 01:46:14 +0000
52+++ ubuntu-packaging-guide/index.rst 2012-06-26 16:03:20 +0000
53@@ -43,6 +43,7 @@
54 security-and-stable-release-updates
55 patches-to-packages
56 libraries
57+ backports
59 Knowledge Base
60 --------------


People subscribed via source and target branches