release manager for 3.5.0

[Raúl Gutiérrez Segalés <rg...@itevenworks.net>]

Hi all,

While work is underway to get a 3.4.6 release out the door, I was thinking
of helping out as release manager for 3.5.0. Here's a rough plan to getting
it done:

For 3.5.0 there are 262 unresolved issued. Some of them are pretty ancient
so maybe the available patch doesn't apply cleanly or doesn't apply at all.
For the easy/clean cases I can check if tests are good, do another review
(if necessary) and ping the commiter who last touched the related files or
logical section to get another glance and hopefully a commit. In parallel,
for the ancient patches which don't apply cleanly and need a lot of work we
can decide on punting for 3.5.1 depending on how critical or not they are.
And we can reiterate here until we get a tractable list of issues for 3.5.0.

After a first iteration/triage we'll have a better idea of the amount of
work left and we can come up with a potential release date and eventually
commit ourselves to that. We'll also need to pay special attention to
ensure that the migration path from 3.4.6 to 3.5.0 is smooth.

Does it sound reasonable? If it does, I'll start with the triage so prepare
yourself to see some activity in JIRA :-)

Cheers,
-rgs

Re: release manager for 3.5.0

[Patrick Hunt <ph...@apache.org>]

On Thu, Feb 6, 2014 at 9:26 AM, Raúl Gutiérrez Segalés
<rg...@itevenworks.net> wrote:
> Hi all,
>
> While work is underway to get a 3.4.6 release out the door, I was thinking
> of helping out as release manager for 3.5.0. Here's a rough plan to getting
> it done:
>

Hi Raul, while we welcome your help only committers on an Apache
project can be RMs. Also, I signed up for being the RM for 3.5 some
time back, we've just been waiting for 3.4.6 to settle before really
pushing on that. This is also why you've seen me moving some of the
3.5 related jiras forward. (there's a list around somewhere the last
time we discussed this, I'll see if I can find it.. here it is
http://markmail.org/message/dob33gq4rjujjs4y). That said you've been
doing a great job and I don't want to discourage you from further
help. We will really need it to get this next major (well technical
minor, but you know what I mean) release out. I'm really excited to
see some of our new features ship.

> For 3.5.0 there are 262 unresolved issued. Some of them are pretty ancient
> so maybe the available patch doesn't apply cleanly or doesn't apply at all.
> For the easy/clean cases I can check if tests are good, do another review
> (if necessary) and ping the commiter who last touched the related files or
> logical section to get another glance and hopefully a commit. In parallel,
> for the ancient patches which don't apply cleanly and need a lot of work we
> can decide on punting for 3.5.1 depending on how critical or not they are.
> And we can reiterate here until we get a tractable list of issues for 3.5.0.
>

That's great. Please do. Likely we will do an number of "alpha"
releases, then some "beta" releases before having a "stable" 3.5.x.
This is what we've done historically (or at least that's what we did
with 3.4).

> After a first iteration/triage we'll have a better idea of the amount of
> work left and we can come up with a potential release date and eventually
> commit ourselves to that. We'll also need to pay special attention to
> ensure that the migration path from 3.4.6 to 3.5.0 is smooth.
>
> Does it sound reasonable? If it does, I'll start with the triage so prepare
> yourself to see some activity in JIRA :-)
>

Cleaning up and such is certainly good to start. However let's focus
our efforts on supporting Flavio and getting 3.4.6 finalized. Then I
will start to ramp up the call for action for 3.5.0+.

Regards,

Patrick