[RFC] Releases planning

[John Arbash Meinel]

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

On 10/7/2010 10:52 AM, Vincent Ladeuil wrote:
>>>>>> Voelker, Bernhard <bernhard.voelker at siemens-enterprise.com> writes:
> 
> <snip/>
> 
>     > I'm just a silent reader, but I come to the question
>     >   "why are parallel releases leading to collisions"?
> 
>     > Isn't there a RM for every series 2.[0123]?
> 
> As of today, there is one RM for all series, but as mentioned in the
> discussion, some RMs *prefer* to release all at once.
> 
>     > If it's due to packagers, then can't the build not be better
>     > automated?
> 
> We're working on it :)
> 

And even when it is automated, it is still a bunch of stuff to kick off.
4 releases by about 6+ platforms is 24 builds. (mac, win, lucid,
maverick, ?, debian, etc).

The windows builds also encounter a fair amount of manual uploading
(because we want to gpg sign it, etc).

I would say that regardless of whether a given RM wants to do all the
releases, the load on *packagers* is definitely at least linear in the
number of releases.

John
=:->

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

iEYEARECAAYFAkyt8pgACgkQJdeBCYSNAAOI9gCggqARVRsqqj9Ut5Z2G/SLxx7A
hnYAnjVd4w6f2iONy3XOI315svh1wR7r
=SQfD
-----END PGP SIGNATURE-----