accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <josh.el...@gmail.com>
Subject Re: 1.5.3 and 1.6.3
Date Wed, 27 May 2015 20:38:46 GMT
SGTM -- makes sense given historically what we've actually ended up doing.

Thanks for sending out a progress update.

Christopher wrote:
> FWIW, I'm still triage'ing issues. I've finished all the 1.5.x issues,
> and have moved on to 1.6.x issues.
>
> For many of these, I just don't see a fixVersion happening for 1.6.3,
> or even 1.6.4 or 1.6.5 (if those occur). So, I'll most likely just
> drop 1.6.x from the fixVersion for these to avoid constant bumping. In
> fact, I'll probably just drop all but the most recent working
> branch... currently 1.8.0/master... for many of them.
>
> It's not that these *can't be* fixed for 1.6.x, it's just that I don't
> see that it is very probably that they will be, so rather than lie to
> ourselves, I'd prefer to just be realistic and drop the older
> fixVersions, rather than constantly bump them when we do bugfix
> releases. If these get fixed, and they are fixed for an earlier
> branch, great, we can update the fixVersion to include them.
>
> The way I see it, the fixVersion has two roles: planning/declared
> intent (for unresolved issues), and statement about which branch a fix
> is included in (for resolved issues). I obviously won't change any
> resolved issues. This is just about being realistic for unresolved
> issues.
>
> If I run into any critical or blocker issues, I probably won't bump or
> drop those (at least, not without discussion on the issue), but
> trivial or non-bug, or "unlikely to be fixed in an older version"
> issues, those are the ones I plan to drop the old fixVersions on.
>
> This is just triage... not final decisions... if I make a change you
> wish to contest, please watch/follow the JIRA notifications and jump
> in to comment (ideally, volunteering to fix the issue in question).
> For some issues I've already passed, this has already happened, which
> is great.
>
> Anyway, this is just an update on what my intentions are, in case
> anybody is curious about all the JIRA edits lately, and in the next
> few days.
>
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Thu, May 21, 2015 at 1:22 PM, Christopher<ctubbsii@apache.org>  wrote:
>> I know Corey volunteered, but I'd like to get started today releasing
>> 1.6.3. So, if there's no objection in the next hour or so, I'm just
>> going to move forward and produce an rc0 test release (no voting
>> necessary, as it won't be released, but testing is welcome).
>>
>> --
>> Christopher L Tubbs II
>> http://gravatar.com/ctubbsii
>>
>>
>> On Tue, May 12, 2015 at 10:17 PM, Corey Nolet<cjnolet@gmail.com>  wrote:
>>> That is, unless any of the new committers would like to take it on- in that
>>> case, I can help ;-)
>>>
>>> On Tue, May 12, 2015 at 3:41 PM, Corey Nolet<cjnolet@gmail.com>  wrote:
>>>
>>>> I can get a 1.6.3 together.
>>>>
>>>>
>>>> On Tue, May 12, 2015 at 2:04 PM, Christopher<ctubbsii@apache.org> 
wrote:
>>>>
>>>>> Sure, we can discuss that separately. I'll start a new thread.
>>>>>
>>>>> --
>>>>> Christopher L Tubbs II
>>>>> http://gravatar.com/ctubbsii
>>>>>
>>>>>
>>>>> On Tue, May 12, 2015 at 1:58 PM, Sean Busbey<busbey@cloudera.com>
 wrote:
>>>>>> let's please have a labeled [DISCUSS] thread on when and how to EOL
1.5.
>>>>>>
>>>>>> On Tue, May 12, 2015 at 12:55 PM, Christopher<ctubbsii@apache.org>
>>>>> wrote:
>>>>>>> And, whether or not we release 1.5.3, I do think we should consider
>>>>>>> closing out development on that branch after 1.7.0 is released.
>>>>>>> Anybody have any thoughts on that?
>>>>>>>
>>>>>>> --
>>>>>>> Christopher L Tubbs II
>>>>>>> http://gravatar.com/ctubbsii
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 12, 2015 at 1:48 PM, Christopher<ctubbsii@apache.org>
>>>>> wrote:
>>>>>>>> I'd like to think about releasing 1.5.3 and 1.6.3, since
there are 75
>>>>>>>> and 82 commits in those branches, presumably fixing a lot
of bugs.
>>>>>>>>
>>>>>>>> Is anybody willing to act as release manager for either of
these and
>>>>>>>> prepare the RCs? Perhaps somebody who hasn't already done
some
>>>>>>>> releases who wants to try?
>>>>>>>>
>>>>>>>> --
>>>>>>>> Christopher L Tubbs II
>>>>>>>> http://gravatar.com/ctubbsii
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sean
>>>>

Mime
View raw message