+1 nb — to both the document and the benefits listed in Scott’s email. Jordan
On Fri, Oct 4, 2019 at 2:26 PM Scott Andreas <sc...@paradoxica.net> wrote: > There are two main benefits to agreeing on this: > > 1. Providing clarity for contributors on release phases – i.e., what types > of changes are expected to land or be deferred during a particular point in > that cycle. > > 2. Providing semantic clarity to users of Cassandra in terms of what they > can expect from a given release. > > The second one is more important. The document stands as a commitment > between the Cassandra project and its users regarding what can be expected > from each type of release. It defines GA releases as "recommended for > production deployment for all users," setting a standard of quality that we > aim to uphold together and that users can depend on. Affirming what it > means for a release to be EOL, deprecated, or in maintenance signals > importance of upgrading to a GA version. > > The prerelease phases set expectations for us as contributors to produce a > more stable release: what type of testing/validation is needed at what > time, at which point interfaces/protocols solidify, when a release is > considered feature complete, etc. > > Creating clarity for ourselves will help us build a better database, and > creating clarity for our users will help give them the confidence to run it. > > I want to thank Sumanth for his work on this document and to everyone else > who's contributed. > > I support it (+1 nb). > > – Scott > > ________________________________________ > From: Stefan Podkowinski <s...@apache.org> > Sent: Tuesday, October 1, 2019 1:43 PM > To: dev@cassandra.apache.org > Subject: Re: [VOTE] Apache Cassandra Release Lifecycle > > What exactly will be the implication of the outcome of this vote, in > case the content is agreed upon? What's the proposal of the voting? > > The document seems to be informative rather then formal. It's verbose on > definitions that should be commonly understood or can only broadly > defined (what is alpha/beta/RC, GA for production, etc.), while at the > same time is unclear and weasel-wordy on our actual commitment and rules. > > > On 30.09.19 20:51, sankalp kohli wrote: > > Hi, > > We have discussed in the email thread[1] about Apache Cassandra > Release > > Lifecycle. We came up with a doc[2] for it. Please vote on it if you > agree > > with the content of the doc[2]. > > > > Thanks, > > Sankalp > > > > [1] > > > https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E > > [2] > > > https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
