Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 17 Jan 2016 00:12:42 +0000 (UTC)
From: Anuj Wadehra <anujw_2003@yahoo.co.in>
To: "dev@cassandra.apache.org" <dev@cassandra.apache.org>,
	Michael Kjellman <mkjellman@internalcircle.com>,
	"dev@cassandra.apache.org" <dev@cassandra.apache.org>
Cc: Jonathan Ellis <jbellis@gmail.com>
Message-ID: <1308821564.5516919.1452989562955.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <7B371511-EB70-4206-8A57-B07E81A3B0BB@internalcircle.com>
References: <7B371511-EB70-4206-8A57-B07E81A3B0BB@internalcircle.com>
Subject: Re: Versioning policy?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_5516918_1342192195.1452989562946"

------=_Part_5516918_1342192195.1452989562946
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I was not referring to Enterprise support here. When I said Open source "pr=
oduct" by mistake, I was just referring to some other Apache open source pr=
ojects like Apache Cassandra where you get EOL announcements, info etc on t=
he main Apache web site. I think all four points are very relevant in conte=
xt of an Open source project and thats why I wanted to thoughts on these po=
ints.


ThanksAnuj

Sent from Yahoo Mail on Android=20
=20
  On Sun, 17 Jan, 2016 at 1:43 am, Michael Kjellman<mkjellman@internalcircl=
e.com> wrote:   Correct, this is an open source project.=20

If you want a Enterprise support story Datastax has an Enterprise option fo=
r you.=20

> On Jan 16, 2016, at 11:19 AM, Anuj Wadehra <anujw_2003@yahoo.co.in> wrote=
:
>=20
> Hi Jonathan
>=20
> It would be really nice if you could share your thoughts on the four poin=
ts raised regarding the Cassandra EOL process. I think similar things happe=
n for other open source products and it would be really nice if we could st=
reamline such things for Apache Cassandra.
>=20
> ThanksAnuj
>=20
> Sent from Yahoo Mail on Android=20
>=20
>=C2=A0 On Thu, 14 Jan, 2016 at 11:28 pm, Anuj Wadehra<anujw_2003@yahoo.co.=
in> wrote:=C2=A0 Hi Jonathan,
> Thanks for the crisp communication regarding the tick tock release & EOL.
> I think its worth considering some points regarding EOL policy and it wou=
ld be great if you can share your thoughts on below points:
> 1.=C2=A0 EOL of a release should be based on "most stable"/"production re=
ady" version date rather than "GA" date of subsequent major releases.
> 2.=C2=A0 I think we should have "Formal EOL Announcement" on Apache Cassa=
ndra website.=C2=A0=20
> 3. "Formal EOL Announcement" should come at least 6 months before the EOL=
, so that users get reasonable time to=C2=A0 =C2=A0 =C2=A0 upgrade.
> 4. EOL Policy (even if flexible) should be stated on Apache Cassandra web=
site
>=20
> EOL thread on users mailing list ended with the conclusion of raising a W=
ishlist JIRA but I think above points are more about working on policy and =
processes rather than just a wish list.=20
>=20
> ThanksAnuj
>=20
>=20
>=20
> Sent from Yahoo Mail on Android=20
>=20
>=C2=A0 On Thu, 14 Jan, 2016 at 10:57 pm, Jonathan Ellis<jbellis@gmail.com>=
 wrote:=C2=A0 Hi Maciek,
>=20
> First let's talk about the tick-tock series, currently 3.x.=C2=A0 This is=
 pretty
> simple: outside of the regular monthly releases, we will release fixes fo=
r
> critical bugs against the most recent bugfix release, the way we did
> recently with 3.1.1 for CASSANDRA-10822 [1].=C2=A0 No older tick-tock rel=
eases
> will be patched.
>=20
> Now, we also have three other release series currently being supported:
>=20
> 2.1.x: supported with critical fixes only until 4.0 is released, projecte=
d
> in November 2016 [2]
> 2.2.x: maintained until 4.0 is released
> 3.0.x: maintained for 6 months after 4.0, i.e. projected until May 2017
>=20
> I will add this information to the releases page [3].
>=20
> [1]
> https://mail-archives.apache.org/mod_mbox/incubator-cassandra-user/201512=
.mbox/%3CCAKkz8Q3StqRFHfMgCMRYaaPdg+HE5N5muBtFVt-=3Dv690PZpozA@mail.gmail.c=
om%3E
> [2] 4.0 will be an ordinary tick-tock release after 3.11, but we will be
> sunsetting deprecated features like Thrift so bumping the major version
> seems appropriate
> [3] http://cassandra.apache.org/download/
>=20
>> On Sun, Jan 10, 2016 at 9:29 PM, Maciek Sakrejda <maciek@heroku.com> wro=
te:
>>=20
>> There was a discussion recently about changing the Cassandra EOL policy =
on
>> the users list [1], but it didn't really go anywhere. I wanted to ask he=
re
>> instead to clear up the status quo first. What's the current versioning
>> policy? The tick-tock versioning blog post [2] states in passing that tw=
o
>> major releases are maintained, but I have not found this as an official
>> policy stated anywhere. For comparison, the Postgres project lays this o=
ut
>> very clearly [3]. To be clear, I'm not looking for any official support,
>> I'm just asking for clarification regarding the maintenance policy: if a
>> critical bug or security vulnerability is found in version X.Y.Z, when c=
an
>> I expect it to be fixed in a bugfix patch to that major version, and whe=
n
>> do I need to upgrade to the next major version.
>>=20
>> [1]: http://www.mail-archive.com/user@cassandra.apache.org/msg45324.html
>> [2]: http://www.planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/
>> [3]: http://www.postgresql.org/support/versioning/
>=20
>=20
>=20
> --=20
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced
>=C2=A0 =C2=A0  =20

------=_Part_5516918_1342192195.1452989562946--