-
Re: Clean up versions in ticketsJesse Yates 2011-11-14, 22:22
At the very least, the commits should have some way for downstream maintainers to figure out what patches need to be applied to keep up, etc
I don't think we need to wholesale change tickets. Affects version is a pretty good indicator- if a patch is rolled in for a given version (and not all of them), then that version should go into the 'fixes version' section on submit. However, we still want to keep track of tickets that affect a version but aren't fixed in that version ("known bugs").
So by all means, let's clean them up if they need it - it can only help.
- Jesse Yates
Sent from my iPhone.
On Nov 14, 2011, at 11:44 AM, Keith Turner <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 14, 2011 at 2:29 PM, Adam Fuchs <[EMAIL PROTECTED]> wrote:
>> On Nov 14, 2011 2:12 PM, "Keith Turner" <[EMAIL PROTECTED]> wrote:
>>>
>>> When we first started creating tickets we would put 1.3.5 and 1.4.0 in
>>> the "Affects Version" field. The following ticket is an example of
>>> this.
>>>
>>> https://issues.apache.org/jira/browse/ACCUMULO-4
>>>
>>> However versions 1.3.5 and 1.4.0 are not released yet and this ticket
>>> is fixed. When 1.3.5 and 1.4.0 are released, this issue will be fixed
>>> in those releases. So this issue does not affect those releases. I
>>> would like go through and correct the tickets that have this type of
>>> inconsistency. The fix I propose is to remove everything from the
>>> "Affects Version" field since their is no released version. Tickets
>>> that are not fixed and will affect version 1.3.5 and 1.4.0 when
>>> released will be left alone. Let me know what you think, if I do not
>>> hear anything in a few days I will start changing the tickets.
>>>
>>> Keith
>>
>> Sounds reasonable to me, especially for the 1.4.0 ones. Should we add
>> previously released versions where applicable to maintain continuity for
>> existing users, our would that be too hard? Maybe just one pre-1.3.5
>> version would suffice?
>>
>> Adam
>>
>
> We discussed adding a 1.3.4 version, but that may be confusing since
> there is no accumulo 1.3.4 released version. I may not be needed, if
> existing users can find what they need by searching for tickets where
> the fix version is 1.3.5. For documentation purposes accumulo 1.3.5
> may contain bug fixes that do not have tickets, do we want to create
> tickets?
I don't think we need to wholesale change tickets. Affects version is a pretty good indicator- if a patch is rolled in for a given version (and not all of them), then that version should go into the 'fixes version' section on submit. However, we still want to keep track of tickets that affect a version but aren't fixed in that version ("known bugs").
So by all means, let's clean them up if they need it - it can only help.
- Jesse Yates
Sent from my iPhone.
On Nov 14, 2011, at 11:44 AM, Keith Turner <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 14, 2011 at 2:29 PM, Adam Fuchs <[EMAIL PROTECTED]> wrote:
>> On Nov 14, 2011 2:12 PM, "Keith Turner" <[EMAIL PROTECTED]> wrote:
>>>
>>> When we first started creating tickets we would put 1.3.5 and 1.4.0 in
>>> the "Affects Version" field. The following ticket is an example of
>>> this.
>>>
>>> https://issues.apache.org/jira/browse/ACCUMULO-4
>>>
>>> However versions 1.3.5 and 1.4.0 are not released yet and this ticket
>>> is fixed. When 1.3.5 and 1.4.0 are released, this issue will be fixed
>>> in those releases. So this issue does not affect those releases. I
>>> would like go through and correct the tickets that have this type of
>>> inconsistency. The fix I propose is to remove everything from the
>>> "Affects Version" field since their is no released version. Tickets
>>> that are not fixed and will affect version 1.3.5 and 1.4.0 when
>>> released will be left alone. Let me know what you think, if I do not
>>> hear anything in a few days I will start changing the tickets.
>>>
>>> Keith
>>
>> Sounds reasonable to me, especially for the 1.4.0 ones. Should we add
>> previously released versions where applicable to maintain continuity for
>> existing users, our would that be too hard? Maybe just one pre-1.3.5
>> version would suffice?
>>
>> Adam
>>
>
> We discussed adding a 1.3.4 version, but that may be confusing since
> there is no accumulo 1.3.4 released version. I may not be needed, if
> existing users can find what they need by searching for tickets where
> the fix version is 1.3.5. For documentation purposes accumulo 1.3.5
> may contain bug fixes that do not have tickets, do we want to create
> tickets?
