You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by mck <mc...@apache.org> on 2017/04/28 13:21:25 UTC
Move 3.11.x unresolved features and improvements to 4.0
Has anyone any objection to moving all open 3.11.x features and
improvements to 4.0?
To my understanding 3.11.0 was intended as the last tick-tock release
and also to form a LTS release by which patches could be applied, ie
3.11.1, 3.11.2, 3.11.3, etc.
As the last tick-tock release there's a presumption here that, as an
odd-numbered release, it would only contain bug fixes. Hence my surprise
to see so many non-bug tickets against it. Furthermore a bug-fix-only
3.11.0 would also help give the LTS release stability.
It's possible that this was simply because tickets got bulk changed from
3.X to 3.11.x, but if not could anyone enlighten us please.
This was discussed a little on irc today:
https://wilderness.apache.org/channels/?f=cassandra-dev/2017-04-28#1493343857
regards,
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Move 3.11.x unresolved features and improvements to 4.0
Posted by Benjamin Lerer <be...@datastax.com>.
Sorry, I misunderstood the email. Aleksey, took care of the commited
patches.
I agree all the open 3.11.x features and improvements should be moved to
4.0.
On Fri, Apr 28, 2017 at 5:04 PM, Benjamin Lerer <benjamin.lerer@datastax.com
> wrote:
> I think that Aleksey already took care of it.
>
> On Fri, Apr 28, 2017 at 3:21 PM, mck <mc...@apache.org> wrote:
>
>>
>>
>> Has anyone any objection to moving all open 3.11.x features and
>> improvements to 4.0?
>>
>> To my understanding 3.11.0 was intended as the last tick-tock release
>> and also to form a LTS release by which patches could be applied, ie
>> 3.11.1, 3.11.2, 3.11.3, etc.
>>
>> As the last tick-tock release there's a presumption here that, as an
>> odd-numbered release, it would only contain bug fixes. Hence my surprise
>> to see so many non-bug tickets against it. Furthermore a bug-fix-only
>> 3.11.0 would also help give the LTS release stability.
>>
>> It's possible that this was simply because tickets got bulk changed from
>> 3.X to 3.11.x, but if not could anyone enlighten us please.
>>
>> This was discussed a little on irc today:
>> https://wilderness.apache.org/channels/?f=cassandra-dev/2017
>> -04-28#1493343857
>>
>> regards,
>> Mick
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>>
>
Re: Move 3.11.x unresolved features and improvements to 4.0
Posted by Michael Shuler <mi...@pbandjelly.org>.
On 04/30/2017 05:29 PM, mck wrote:
>
> Narrowing down the list to only
> - types: Feature, Improvements, Task, Wish, Sub-task,
> - versions: 3.11.0 and 3.11.x, and
> - status: Opened, In Progress, Reopened
>
> there's 235 issues.
>
> https://issues.apache.org/jira/browse/CASSANDRA-13481?jql=project%20%3D%20CASSANDRA%20AND%20issuetype%20in%20(Improvement%2C%20%22New%20Feature%22%2C%20Task%2C%20Wish%2C%20Sub-task)%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20in%20(3.11.0%2C%203.11.x)
That just opens 13481 for me. This link may be better for just the jql list:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20issuetype%20in%20(Improvement%2C%20%22New%20Feature%22%2C%20Task%2C%20Wish%2C%20Sub-task)%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20in%20(3.11.0%2C%203.11.x)
> The agreement so far is to move these issues to Fix Version 4.x
> Note, this bulk change would replace all previously marked fix versions
> with just "4.x".
>
> I can do this tomorrow if I hear no objections.
>
> I'm sure a few of the issues have reason to go into 3.0.x and/or 3.11.0
> (doc tasks, etc), and I presume it's ok that the assignee re-corrects
> each such ticket.
Looks good to me! Thanks for narrowing the search down for a better view.
--
Kind regards,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Move 3.11.x unresolved features and improvements to 4.0
Posted by mck <mc...@apache.org>.
> I can do this tomorrow if I hear no objections.
Done.
regards,
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Move 3.11.x unresolved features and improvements to 4.0
Posted by mck <mc...@apache.org>.
On Sat, 29 Apr 2017, at 01:14, Michael Shuler wrote:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.11.x
>
> Currently 374 tickets - this is the list we're talking about. Anything
> that's not a bug fix intended for the cassandra-3.11 branch should
> probably be moved to trunk/4.0.
Narrowing down the list to only
- types: Feature, Improvements, Task, Wish, Sub-task,
- versions: 3.11.0 and 3.11.x, and
- status: Opened, In Progress, Reopened
there's 235 issues.
https://issues.apache.org/jira/browse/CASSANDRA-13481?jql=project%20%3D%20CASSANDRA%20AND%20issuetype%20in%20(Improvement%2C%20%22New%20Feature%22%2C%20Task%2C%20Wish%2C%20Sub-task)%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20in%20(3.11.0%2C%203.11.x)
The agreement so far is to move these issues to Fix Version 4.x
Note, this bulk change would replace all previously marked fix versions
with just "4.x".
I can do this tomorrow if I hear no objections.
I'm sure a few of the issues have reason to go into 3.0.x and/or 3.11.0
(doc tasks, etc), and I presume it's ok that the assignee re-corrects
each such ticket.
regards,
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Move 3.11.x unresolved features and improvements to 4.0
Posted by Michael Shuler <mi...@pbandjelly.org>.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.11.x
Currently 374 tickets - this is the list we're talking about. Anything
that's not a bug fix intended for the cassandra-3.11 branch should
probably be moved to trunk/4.0.
--
Kind regards,
Michael
On 04/28/2017 10:04 AM, Benjamin Lerer wrote:
> I think that Aleksey already took care of it.
>
> On Fri, Apr 28, 2017 at 3:21 PM, mck <mc...@apache.org> wrote:
>
>>
>>
>> Has anyone any objection to moving all open 3.11.x features and
>> improvements to 4.0?
>>
>> To my understanding 3.11.0 was intended as the last tick-tock release
>> and also to form a LTS release by which patches could be applied, ie
>> 3.11.1, 3.11.2, 3.11.3, etc.
>>
>> As the last tick-tock release there's a presumption here that, as an
>> odd-numbered release, it would only contain bug fixes. Hence my surprise
>> to see so many non-bug tickets against it. Furthermore a bug-fix-only
>> 3.11.0 would also help give the LTS release stability.
>>
>> It's possible that this was simply because tickets got bulk changed from
>> 3.X to 3.11.x, but if not could anyone enlighten us please.
>>
>> This was discussed a little on irc today:
>> https://wilderness.apache.org/channels/?f=cassandra-dev/
>> 2017-04-28#1493343857
>>
>> regards,
>> Mick
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Move 3.11.x unresolved features and improvements to 4.0
Posted by Benjamin Lerer <be...@datastax.com>.
I think that Aleksey already took care of it.
On Fri, Apr 28, 2017 at 3:21 PM, mck <mc...@apache.org> wrote:
>
>
> Has anyone any objection to moving all open 3.11.x features and
> improvements to 4.0?
>
> To my understanding 3.11.0 was intended as the last tick-tock release
> and also to form a LTS release by which patches could be applied, ie
> 3.11.1, 3.11.2, 3.11.3, etc.
>
> As the last tick-tock release there's a presumption here that, as an
> odd-numbered release, it would only contain bug fixes. Hence my surprise
> to see so many non-bug tickets against it. Furthermore a bug-fix-only
> 3.11.0 would also help give the LTS release stability.
>
> It's possible that this was simply because tickets got bulk changed from
> 3.X to 3.11.x, but if not could anyone enlighten us please.
>
> This was discussed a little on irc today:
> https://wilderness.apache.org/channels/?f=cassandra-dev/
> 2017-04-28#1493343857
>
> regards,
> Mick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>