robert burrell donkin ha scritto:
> we need to elect a release manager who can shepherd the release
> through these difficult waters. we need to take a release branch ASAP
> so the short term push towards a release can be separated from medium
> term concerns about design and maintainability.
I agree. How is a release manager elected?
by an election ;-)
typically lazy consensus
What is the "special power" of the release manager vs other committers?
none but none should be needed
- robert
*IMHO* we have the following possible releases:
- 2.3.1 : IMHO everything is ready in v2.3 (as I wrote in the recent
"About 2.3.1" topic) and only need someone to take care of it (I can do
if asked, but I would prefer if someone else do)
- 2.4.0 : (ex next-minor) has been proposed by Noel and Vincenzo. If
they still have this in their plans IMHO one of them can be the release
manager and branch "v2.4" from current "v2.3" and start the "vetted
backports" (as per Noel mails)
- 2.5.0 / 3.0.0: (ex next-major) sooner or later trunk should (IMHO) be
branched to start consolidation and release something. We agreed on this
generically but have not found a solution. Now you are the most active
in trunk, so maybe you will take care of understanding what can be done
and when.
I personally don't care of 2.4.0 (next-minor). I'm willing to help for
2.3.1 if asked, and to help with 2.5.0/3.0.0 (once I'll have understood
what can be done there).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
