Re: [VOTE-2] Apache Cassandra Release Lifecycle

2019-10-09 Thread Mick Semb Wever
> We have discussed in the email thread[1] about Apache Cassandra Release > Lifecycle. We came up with a doc[2] for it. We have finalized the doc > here[3] Please vote on it if you agree with the content of the doc [3]. +1 nb the doc is good. it adds value for users, and does not need to

Re: moving the site from SVN to git

2019-10-09 Thread Jon Haddad
OK, I checked with INFRA on some details and will finish the migration tomorrow. On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad wrote: > Awesome, thanks Michael. > > We need to do a little bit of additional configuration to have it switch > over. Specifically, we need to set up the .asf.yaml

Re: [VOTE-2] Apache Cassandra Release Lifecycle

2019-10-09 Thread Dinesh Joshi
+1, lets evolve the document as we gain more experience with the proposed release lifecycle. Dinesh > On Oct 9, 2019, at 9:41 AM, Jon Haddad wrote: > > +1 works for me > > On Wed, Oct 9, 2019 at 9:30 AM Michael Shuler > wrote: > >> +1 >> >> -- >> Kind regards, >> Michael >> >> On Wed,

Re: Protocol-impacting (internode and client) changes for 4.0

2019-10-09 Thread Dinesh Joshi
+1 Dinesh > On Oct 9, 2019, at 12:41 PM, Joshua McKenzie wrote: > >> >> each one of them is extremely low risk, which means that any validation >> effort that has already happened won't have to be re-done > > +1 > > On Wed, Oct 9, 2019 at 1:46 PM Jon Haddad wrote: > >> Seems reasonable,

Re: Protocol-impacting (internode and client) changes for 4.0

2019-10-09 Thread Joshua McKenzie
> > each one of them is extremely low risk, which means that any validation > effort that has already happened won't have to be re-done +1 On Wed, Oct 9, 2019 at 1:46 PM Jon Haddad wrote: > Seems reasonable, especially since we're in alpha mode. > > On Wed, Oct 9, 2019 at 10:28 AM Aleksey

Re: Protocol-impacting (internode and client) changes for 4.0

2019-10-09 Thread Jon Haddad
Seems reasonable, especially since we're in alpha mode. On Wed, Oct 9, 2019 at 10:28 AM Aleksey Yeshchenko wrote: > +1; in particular since the protocol itself is still in beta > > > On 9 Oct 2019, at 17:26, Oleksandr Petrov > wrote: > > > > Hi, > > > > During NGCC/ACNA19 we've had quite a few

Re: Protocol-impacting (internode and client) changes for 4.0

2019-10-09 Thread Aleksey Yeshchenko
+1; in particular since the protocol itself is still in beta > On 9 Oct 2019, at 17:26, Oleksandr Petrov wrote: > > Hi, > > During NGCC/ACNA19 we've had quite a few conversations around the 4.0 > release. Many (minor) features and changes suggested during that time are > possible to implement

Re: Protocol-impacting (internode and client) changes for 4.0

2019-10-09 Thread Benedict Elliott Smith
+1 On 09/10/2019, 17:50, "Oleksandr Petrov" wrote: Hi, During NGCC/ACNA19 we've had quite a few conversations around the 4.0 release. Many (minor) features and changes suggested during that time are possible to implement in 4.next without any problem. However, some changes

Protocol-impacting (internode and client) changes for 4.0

2019-10-09 Thread Oleksandr Petrov
Hi, During NGCC/ACNA19 we've had quite a few conversations around the 4.0 release. Many (minor) features and changes suggested during that time are possible to implement in 4.next without any problem. However, some changes that seem to be very important for the community, which got mentioned in

Re: [VOTE-2] Apache Cassandra Release Lifecycle

2019-10-09 Thread Michael Shuler
+1 -- Kind regards, Michael On Wed, Oct 9, 2019 at 9:06 AM Aleksey Yeshchenko wrote: > > +1 as a rather reasonable starting point; we can make changes to the process > in the future if need be. > > > On 8 Oct 2019, at 19:00, sankalp kohli wrote: > > > > Hi, > >We have discussed in the

Re: [VOTE-2] Apache Cassandra Release Lifecycle

2019-10-09 Thread Aleksey Yeshchenko
+1 as a rather reasonable starting point; we can make changes to the process in the future if need be. > On 8 Oct 2019, at 19:00, 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. We have