launchpad development|
⇤ ← Revision 1 as of 2011-08-18 08:49:17
Size: 1331
Comment:
|
Size: 1328
Comment: tune uup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 23: | Line 23: |
| After changes land and pass through buildbot, they will soon be available on https://bazaar.staging.launchpad.net (do note that only bzr branches are backed with the real bzr data on staging — for testing other branches, push your stuff using `bzr push lp://staging/~you/+junk/blah`) | 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`) |
| Line 25: | Line 25: |
| FIXME: what about qastaging? clarification needed if loggerhead PQM runs against db-stable Launchpad or stable Launchpad. | |
| Line 29: | Line 28: |
| To get changes deployed, do... FIXME. | Codebrowse changes are deployed by launchpads regular 'nodowntime' deployment process. |
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)
Landing changes for Launchpad
For deploying loggerhead to bazaar.launchpad.net, one has to land changes on 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.
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.
