launchpad development|
⇤ ← Revision 1 as of 2009-08-10 16:50:10
Size: 1488
Comment: Initial draft of new page, with TODO notice about incoming material.
|
Size: 1605
Comment: Add a link to open bug about this page.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| '''''TODO:''''' ''The relationships between these four branches are given in this internal wiki page, along with great diagrams: https://wiki.canonical.com/Launchpad/Experiments/DBDevel . I am transferring that information over right now. -kfogel'' | '''''TODO:''''' ''The relationships between these four branches are given in this internal wiki page, along with great diagrams: https://wiki.canonical.com/Launchpad/Experiments/DBDevel . I am transferring that information over right now. Also, I'll finish out [[https://bugs.edge.launchpad.net/launchpad-documentation/+bug/408069|bug #408069]] when done. -kfogel'' |
This page describes the "master" branches for Launchpad development. Please ask for help immediately if you have any questions. |
Where's trunk?
Launchpad has four master branches (this is unusual; most projects only have one). All four are owned by launchpad-pqm, the Patch Queue Manager. They are:
devel Where most development takes place (except anything that involves changing the database schema; see below).
db-devel Changes that modify the database schema get merged here first. Note: this is also the default stacking branch for other Launchpad branches.
stable This is what we roll out to production servers when we do a release.
db-stable ??? (see below)
TODO: The relationships between these four branches are given in this internal wiki page, along with great diagrams: https://wiki.canonical.com/Launchpad/Experiments/DBDevel . I am transferring that information over right now. Also, I'll finish out bug #408069 when done. -kfogel
