You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Nate McCall <zz...@gmail.com> on 2017/06/21 02:11:15 UTC
[DISCUSS] Should we do a 2.2 release?
Since we have the others going out and we do have some bugfixes there.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [DISCUSS] Should we do a 2.2 release?
Posted by Nate McCall <zz...@gmail.com>.
> Should we also do a 2.1.18 release as a final cut and end commits to the
> cassandra-2.1 branch? I'm sorry I hadn't thought about this sooner.
Meh? There is nothing major in there. That said, if we want to just
say "that's it for 2.1", I guess we could do another.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [DISCUSS] Should we do a 2.2 release?
Posted by Michael Shuler <mi...@pbandjelly.org>.
Yeah, the number of users running 2.1 was part of my concern, and if
we're happy to maintain 4 actively supported branches, along with trunk,
I think that's fine.
A 2.1.18 release with the few fixes committed in cassandra-2.1 will at
least be an opportunity to get RPMs rolled up for users in all branches.
I appreciate the feedback.
--
Michael
On 06/21/2017 12:01 AM, Jeff Jirsa wrote:
> Site says:
>
> * Apache Cassandra 2.1 is supported until 4.0 release (date
> TBD) with critical fixes only.
>
> Since we don't know when 4.0 goes out, we shouldn't be in a hurry to do
> a final 2.1.18 cut. There's not much in that branch (a few 2i fixes,
> some build fixes, a cqlsh fix, and a logging fix), so no reason to cut
> it now, and certainly no reason to cut a "final" release now. Leave it
> open, there's no real cost to having it open, and if a real critical bug
> pops up between now and 4.0, the hundreds/thousands of people running
> 2.1 in prod will appreciate a fix.
>
> - Jeff
>
>
>
> On Tue, Jun 20, 2017 at 8:20 PM, Michael Shuler <michael@pbandjelly.org
> <ma...@pbandjelly.org>> wrote:
>
> Sounds good to me - I'll work up a 2.2.10 artifact set tomorrow.
>
> Looking at our current branches and the EOL TBD dates on the download
> page, I believe the 4.0 references for sunsetting branches was prior to
> considering a 3.11.0 release with ongoing support for the branch.
>
> Should we also do a 2.1.18 release as a final cut and end commits to the
> cassandra-2.1 branch? I'm sorry I hadn't thought about this sooner.
>
> Michael
>
> On 06/20/2017 09:11 PM, Nate McCall wrote:
> > Since we have the others going out and we do have some bugfixes there.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> <ma...@cassandra.apache.org>
> For additional commands, e-mail: dev-help@cassandra.apache.org
> <ma...@cassandra.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [DISCUSS] Should we do a 2.2 release?
Posted by kurt greaves <ku...@instaclustr.com>.
+1 what Jeff said.
Re: [DISCUSS] Should we do a 2.2 release?
Posted by Jeff Jirsa <jj...@gmail.com>.
Site says:
- Apache Cassandra 2.1 is supported until 4.0 release (date TBD)
with critical
fixes only.
Since we don't know when 4.0 goes out, we shouldn't be in a hurry to do a
final 2.1.18 cut. There's not much in that branch (a few 2i fixes, some
build fixes, a cqlsh fix, and a logging fix), so no reason to cut it now,
and certainly no reason to cut a "final" release now. Leave it open,
there's no real cost to having it open, and if a real critical bug pops up
between now and 4.0, the hundreds/thousands of people running 2.1 in prod
will appreciate a fix.
- Jeff
On Tue, Jun 20, 2017 at 8:20 PM, Michael Shuler <mi...@pbandjelly.org>
wrote:
> Sounds good to me - I'll work up a 2.2.10 artifact set tomorrow.
>
> Looking at our current branches and the EOL TBD dates on the download
> page, I believe the 4.0 references for sunsetting branches was prior to
> considering a 3.11.0 release with ongoing support for the branch.
>
> Should we also do a 2.1.18 release as a final cut and end commits to the
> cassandra-2.1 branch? I'm sorry I hadn't thought about this sooner.
>
> Michael
>
> On 06/20/2017 09:11 PM, Nate McCall wrote:
> > Since we have the others going out and we do have some bugfixes there.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: [DISCUSS] Should we do a 2.2 release?
Posted by Michael Shuler <mi...@pbandjelly.org>.
Sounds good to me - I'll work up a 2.2.10 artifact set tomorrow.
Looking at our current branches and the EOL TBD dates on the download
page, I believe the 4.0 references for sunsetting branches was prior to
considering a 3.11.0 release with ongoing support for the branch.
Should we also do a 2.1.18 release as a final cut and end commits to the
cassandra-2.1 branch? I'm sorry I hadn't thought about this sooner.
Michael
On 06/20/2017 09:11 PM, Nate McCall wrote:
> Since we have the others going out and we do have some bugfixes there.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org