launchpad-dev team mailing list archive

[John Arbash Meinel <john@xxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>> Launchpad will at some point in the future add an edge codehost, which
>> will run Launchpad's own tip, then be merged to the lpnet (ie stable)
>> servers in monthly releases.  edge will run only slightly ahead with
>> the bzr version, for example being on 2.1b2 when lpnet is on 2.1b1.
>> This gives some opportunity for testing.
>>
> 
> FWIW, the edge codehosting service is waiting on our IS team to do
> some network configuration.
> 
>> The biggest risk seems to be that a change in 2.1.x may introduce
>> bugs, either to do with operation with old clients or otherwise.  The
>> best way to address this is (aside from general quality development)
>> to test each release as it's integrated on the staging and edge
>> codehost.  At least this way we will find any such issues earlier in
>> bzr's cycle rather than at the 2.1rc1 point.
>>
>> It may be interesting in the future to allow the client to specify the
>> remote bzr commandname as eg 'bzr-2.0' and then we could have several
>> available servers on the Launchpad side; this would require including
>> multiple bzr trees in the deployment.
>>
> 
> This would indeed be interesting. It would require a lot of work.
> 
> jml
> 


Well, we already have BZR_REMOTE_PATH and the internal config
"bzr_remote_path". I don't know the specifics of what it would take on
Launchpad's side. Though I do believe you are spawning a real process
(bzr lp-serve), so it seems reasonable that the client could do:

BZR_REMOTE_PATH=bzr-2.1 bzr branch lp:foo

And on Launchpad's side, it would just have a list of allowed bzr's that
could be spawned.

I would assume that the real problem is the specific "what it takes to
bundle 2 versions of bzr on codehosting."

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq7mHAACgkQJdeBCYSNAAMAlACcCNFMMHdj4AIr/Dj+ONVnS3pK
cy0AmwfLECFKnVpUdjiDYJBrcbraorAy
=5wfP
-----END PGP SIGNATURE-----