launchpad development|
Size: 1328
Comment: tune uup
|
← Revision 3 as of 2011-08-25 12:13:58 ⇥
Size: 1081
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| Launchpad uses the loggerhead trunk branch for deployment. |
|
| Line 14: | Line 16: |
| For deploying loggerhead to bazaar.launchpad.net, one has to land changes on [[https://code.launchpad.net/~launchpad-pqm/loggerhead/devel|lp:~launchpad-pqm/loggerhead/devel]] through PQM, by eg. using {{{ bzr pqm-submit --submit-branch lp:~launchpad-pqm/loggerhead/devel }}} NOTE: do not forget to update `utilities/sourcedeps.conf` in the LP tree to make Launchpad actually use the newly landed revisions. |
Update `utilities/sourcedeps.conf` in the LP tree to make Launchpad actually use the newly landed revision. |
| Line 25: | Line 22: |
Loggerhead for LP developers
Loggerhead is a web-based bazaar code browser.
Landing on trunk
Landing on trunk is done directly by committing and pushing to lp:loggerhead, but make sure you:
- get a review first
- run the test suite before committing your changes (and see that it passes)
Launchpad uses the loggerhead trunk branch for deployment.
Landing changes for Launchpad
Update utilities/sourcedeps.conf in the LP tree to make Launchpad actually use the newly landed revision.
QA
After changes land and pass through buildbot, they will soon be available on https://bazaar.staging.launchpad.net and https://bazaar.qastaging.launchpad.net. (do note that only the bzr projects branches are backed with the real bzr data on staging and qastaging — for testing other branches, push your stuff using bzr push lp://staging/~you/+junk/blah)
Deployment
Codebrowse changes are deployed by launchpads regular 'nodowntime' deployment process.
