Rev 5331: (jameinel) a couple of doc cleanups about the ppa (Martin Pool) in file:///home/pqm/archives/thelove/bzr/%2Btrunk/ Patch Queue Manager pqm at
Sat Jul 3 01:00:56 BST 2010

At file:///home/pqm/archives/thelove/bzr/%2Btrunk/

revno: 5331 [merge]
revision-id: pqm at
parent: pqm at
parent: mbp at
committer: Patch Queue Manager <pqm at>
branch nick: +trunk
timestamp: Sat 2010-07-03 01:00:54 +0100
  (jameinel) a couple of doc cleanups about the ppa (Martin Pool)
  doc/developers/ppa.txt         ppa.txt-20080722055539-606u7t2z32t3ae4w-1
=== modified file 'doc/developers/ppa.txt'
--- a/doc/developers/ppa.txt	2009-12-02 20:34:07 +0000
+++ b/doc/developers/ppa.txt	2010-06-30 04:11:36 +0000
@@ -13,13 +13,13 @@
-As of June 2008, there are three PPAs:
+As of June 2010, there are three PPAs:
-    Final released versions.
+    Final released versions and updates.
-    Releases and release candidates.
+    Beta releases.
     Automatic nightly builds from trunk.
@@ -27,13 +27,16 @@
 We build packages for every supported Ubuntu release
 <>.  Packages need no longer be updated
 when the release passes end-of-life because all users should
-have upgraded by then.  (As of May 2008, Edgy Eft is no longer supported.)
+have upgraded by then.  
-We build a distinct package for each distrorelease.  As of bzr 1.5, Dapper
-uses ``python-support`` and later distributions use ``python-central``.
+We build a distinct package for each distrorelease.  
 If you upload a release-specific version, you should add a suffix to the
 package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
+Dapper uses the ``python-support`` framework and later distributions use
+``python-central``.  This has little effect on everyday packaging but does
+mean that some of the control files are quite different.
 Every package is first uploaded into the beta ppa.  For final release
 versions it is also copied to the main PPA.

More information about the bazaar-commits mailing list