Hi,
Now that we are rethinking versioning and release frequency, there exists an
opportunity to make life easier for Cassandra users.
How often mailing lists are discussing:
"Which Cassandra version is stable for production?"OR"Is x version stable?"
Your release version should indicate your confid
+1 semver and what anuj says
It is commonly known and used, many people know and understand it.
Standards for the win!
2017-01-14 19:07 GMT+01:00 Anuj Wadehra :
> Hi,
> Now that we are rethinking versioning and release frequency, there exists
> an opportunity to make life easier for Cassandra us
> I propose the following artifacts for release as 3.10.
>
+1
Thanks!
+1
Thanks for bringing this up.
On Sat, Jan 14, 2017 at 6:21 AM, Aleksey Yeschenko wrote:
> Hi all!
>
> It seems like we have a general consensus on ending tick-tock at 3.11, and
> moving
> on to stabilisation-only for 3.11.x series.
>
> In light of this, I suggest immediate feature freeze in th
+1
On Fri, Jan 13, 2017 at 6:46 PM, Michael Shuler
wrote:
> I propose the following artifacts for release as 3.10.
>
> sha1: 9c2ab25556fad06a6a4d58f4bb652719a8a1bc27
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
> shortlog;h=refs/tags/3.10-tentative
> Artifacts:
> https://re
+1
--
Jeff Jirsa
> On Jan 13, 2017, at 4:46 PM, Michael Shuler wrote:
>
> I propose the following artifacts for release as 3.10.
>
> sha1: 9c2ab25556fad06a6a4d58f4bb652719a8a1bc27
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
> Artifact
