3.1.x bugs

[Leif Hedstrom <zw...@apache.org>]

Hi all,

In order to get some control of the bugs, and some ideas of where we are 
with a v3.1.3 release, and (hopefully) a not too distant v3.2. release, I 
have done the following in Jira:


     1) I moved all 3.1.4 bugs to 3.1.5.

     2) I moved all 3.1.3 bugs to 3.1.4.


I don't know that we would make a 3.1.5 release (we might). Now, for this to 
work, I need you all to do two things:

     1) Move any bugs from 3.1.4 that you will work (and close) on in the 
next 2 weeks back to v3.1.3.

     2) Move any bugs from 3.1.4 that will not get worked on "any time soon" 
either out to 3.1.5, or 3.3.0, or "sometimes".


I'd like to aim for a v3.2 release by the end of this quarter. Yes, it's a 
bit optimistic, and maybe it means we'll release it in April. But lets try, 
I think we already have enough new features for a v3.2 release, so making 
things stable now is hopefully a priority for everyone. Of course, this is 
all up for discussion, but remember our goal was for a 3.2 release by end of 
Q4/11, and we missed that one (blame me).

Thanks,

-- leif

Re: 3.1.x bugs

[Leif Hedstrom <zw...@apache.org>]

On 2/26/12 2:51 PM, Leif Hedstrom wrote:
> Hi all,
>
> In order to get some control of the bugs, and some ideas of where we are 
> with a v3.1.3 release, and (hopefully) a not too distant v3.2. release, I 
> have done the following in Jira:
>
>
>     1) I moved all 3.1.4 bugs to 3.1.5.
>
>     2) I moved all 3.1.3 bugs to 3.1.4.
>
>
> I don't know that we would make a 3.1.5 release (we might). Now, for this 
> to work, I need you all to do two things:
>
>     1) Move any bugs from 3.1.4 that you will work (and close) on in the 
> next 2 weeks back to v3.1.3.
>
>     2) Move any bugs from 3.1.4 that will not get worked on "any time 
> soon" either out to 3.1.5, or 3.3.0, or "sometimes".

Obviously, you can move any bug from any fix version to 3.1.3/.4, e.g. you 
can definitely move 3.1.5 bugs back to 3.1.4 or 3.1.3.

-- Leif