1
*************************************
2
Bazaar and the Launchpad Code release
3
*************************************
5
Launchpad will be released as open source before the end of July 2009,
6
including all its history.
8
We want to release the source for download through Bazaar.
10
We expect there will be considerable interest in downloading and looking
11
through the source, and then in pushing back branches for integration.
17
* Bazaar's brisbane-core (aka 2.0) format must be stable and reliable
18
before the release is published. It's been tested on several projects
19
but not yet widely used in production.
21
* The format should be branded '2.0' or '2.0beta' not 'development'.
23
* Launchpad must cope reliably with large amounts of load. Much of it will
24
be anonymous access over http, which can be served passively from
25
Apache and more efficiently than from Python.
27
* Stacking must work in bzr brisbane-core
28
<https://bugs.launchpad.net/bzr/+bug/373455>
29
(It's arguably not strictly required, but without it it'll be hard to
30
actually work on the branches, and doing another format change
31
afterwards would be bad.)
33
* "Things don't work the first time." We may need to land more fixes from
34
bzr into Launchpad after initial testing before it's ready to go.
36
* Clients that can read this format should be available for all important
39
* It would be annoying to ask people to upgrade just after downloading all
40
the data: large upgrades of Launchpad's repository take hours at least.
42
* If Launchpad has too many incoming SSH connections, it should fall back
49
* Fix stacking in brisbane-core <https://bugs.launchpad.net/bzr/+bug/373455>
51
* Rename or alias the format to '2.0'.
53
* Fix other critical bugs targetted to 2.0:
54
<https://launchpad.net/bzr/+milestone/2.0>
56
* If these fixes are reasonably small, target them to a 1.15.1rc1 and
57
push it immediately; otherwise merge to 1.16rc1. Release and test.
59
* Merge that release into Launchpad's rocketfuel branch.
61
* Roll out that Launchpad release onto lpnet.
63
* Upgrade Launchpad branches.
65
* Test performance of Launchpad under load, over both ssh and http.
66
Perhaps recruit Canonical people to pull simultaneously from around the
69
* Check performance over dumb http is adequate, both in throughput for the
70
user and load on the server.
72
* Install some load-limiting for ssh, either at the application or the
75
* Announce the Launchpad open source release.
81
It would be nice to support nested trees in this release. If it's ready
82
we'll merge it, but finishing it is not a higher priority than making
83
brisbane-core available in a timely 2.0 and a good Launchpad