bzr-packagers team mailing list archive

[John Arbash Meinel <john@xxxxxxxxxxxxxxxxx>]

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

Ian Clatworthy wrote:
> Hi John,
> 
> Just wanted to pick your brains on how we should build the 2.0.5
> installer now. I'm thinking that we should set up buildout.cfg so that
> "release" is the 2.0 series and "trunk" is the 2.1 series. This will
> work OK because 2.2 is going to to built using the new build.py script.
> 
> Does that sound right? Is there a better way?
> 
> Ian C.
> 

Oh and I should clarify, I think having multiple release vs trunk
targets is actually probably a bad thing.

It was an interesting idea at the time, but now that we have 3 stable
trunks, with different plugin dependencies, etc, we need to deal with that.

Instead, we could have 4 sets of configs, 2.0, 2.1, 2.2, 'tip'. The code
was written thinking we would want answers to:

 does the latest plugin work against the last stable release

and

 does the current tip work with the last stable plugin release

Which would have been nice, but I'd rather see:

 Build release X, which includes released versions Y, Z, ...

 Build tip for everything

John
=:->

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

iEYEARECAAYFAkuro/IACgkQJdeBCYSNAAO+1gCcD3QWYCQmN4J2i8v+v6vVO/Jl
pu0AoND2GLna5c2yDxg1RdICK7I3IL9V
=Ptgk
-----END PGP SIGNATURE-----