~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/ppa.txt

  • Committer: Martin Pool
  • Date: 2010-01-29 14:09:05 UTC
  • mto: This revision was merged to the branch mainline in revision 4992.
  • Revision ID: mbp@sourcefrog.net-20100129140905-2uiarb6p8di1ywsr
Correction to url

from review: https://code.edge.launchpad.net/~mbp/bzr/doc/+merge/18250

Show diffs side-by-side

added added

removed removed

Lines of Context:
13
13
 
14
14
  __ https://help.launchpad.net/PPAQuickStart
15
15
 
16
 
As of June 2010, there are three PPAs:
 
16
As of June 2008, there are three PPAs:
17
17
 
18
18
<https://launchpad.net/~bzr/+archive>
19
 
    Final released versions and updates.
 
19
    Final released versions.
20
20
 
21
21
<https://launchpad.net/~bzr-beta-ppa/+archive>
22
 
    Beta releases.
 
22
    Releases and release candidates.
23
23
 
24
24
<https://launchpad.net/~bzr-nightly-ppa/+archive>
25
25
    Automatic nightly builds from trunk.
27
27
We build packages for every supported Ubuntu release
28
28
<https://wiki.ubuntu.com/Releases>.  Packages need no longer be updated
29
29
when the release passes end-of-life because all users should
30
 
have upgraded by then.  
 
30
have upgraded by then.  (As of May 2008, Edgy Eft is no longer supported.)
31
31
 
32
 
We build a distinct package for each distrorelease.  
 
32
We build a distinct package for each distrorelease.  As of bzr 1.5, Dapper
 
33
uses ``python-support`` and later distributions use ``python-central``.
33
34
If you upload a release-specific version, you should add a suffix to the
34
35
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
35
36
 
36
 
Dapper uses the ``python-support`` framework and later distributions use
37
 
``python-central``.  This has little effect on everyday packaging but does
38
 
mean that some of the control files are quite different.
39
 
 
40
37
Every package is first uploaded into the beta ppa.  For final release
41
38
versions it is also copied to the main PPA.
42
39