See below:

- chip

Sent from my iPhone.

On Oct 31, 2012, at 11:04 PM, Joe Brockmeier <j...@zonker.net> wrote:

> On Wed, Oct 31, 2012 at 08:30:36PM -0400, Chip Childers wrote:
>> Since I just started up the conversation about timing of feature
>> releases, I wanted to start the discussion on how we want to decide
>> what goes into the 4.0 branch and when we would pull the trigger on a
>> 4.0.X bug-fix release process.  Personally, I don't have a
>> particularly strong opinion about when we cut bug fix releases, but I
>> do strongly feel that we should have one or two committers that are
>> the "masters" of the 4.0 branch.  We should be very careful about what
>> goes in there from now on, with a focus on (1) security issues, (2)
>> high priority bugs, and (3) bugs that might be minor, but really annoy
>> the heck out of our users.
>
> Given the need to do a full vote for any release, I'd say anything less
> than one month cycles for bug-fix releases is a bad idea. Longer than
> one month is a long time to wait for a high priority bug if we have a
> fix in hand. So... I'd say a one-month cycle?

Works for me.

>
>> So...  thoughts?  Anyone willing to "own" the 4.0 branch during it's
>> support lifetime?
>
> Now that we're nearly through with the inaugural release, do we have
> a runbook or something that details what the process requires? (Aside
> from the existing Apache docs that spell out the overall Apache
> requirements for releases, I mean.)

The release process is on the wiki. Any committer can follow it
(hopefully). Improvements welcome!

>
> IOW - do we have a job description for someone to volunteer for this?
>
Dunno, but probably:

1) cherry pick appropriate fixes into the branch
2) watch the branch for inappropriate commits, to maintain the goals
of the branch
3) kick off release processes at whatever schedule we finalize.


> Best,
>
> Joe
> --
> Joe Brockmeier
> Twitter: @jzb
> http://dissociatedpress.net/
>

Reply via email to