Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-06-25 Thread Oleksandr Petrov
Maybe a bit off-topic: Before we cut a release, we should make sure we take care of beta protocol [1], include released driver versions [2] and remove compact storage remainders [3]. Third one is optional, but I'd argue we should do it sooner rather than later. [1]

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-06-21 Thread Sumanth Pasupuleti
Thanks for the feedback Scott. I have incorporated all the incremental feedback I have thus far. Looking for any additional feedback folks may have. https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit# On Tue, Jun 11, 2019 at 11:54 AM Scott Andreas wrote: >

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-06-11 Thread Scott Andreas
Thanks for starting this discussion, Sumanth! Added a round of comments as well. Summarizing my non-binding feedback: I feel that many of the items under "Alpha" and "Beta" should be achieved prior to the release of an alpha, especially those related to correctness/safety, scope lock, feature

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-06-11 Thread Joshua McKenzie
Had a few more points of feedback for you Sumanth; trying to get some clarity on how the PMC might function w/relation to the various votes and definitions. Thanks for the integration and continued effort on this - it's looking good! On Tue, Jun 11, 2019 at 9:45 AM Sumanth Pasupuleti <

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-06-11 Thread Sumanth Pasupuleti
Thanks for the feedback on the product stages/ release life cycle document. I have incorporated the suggestions and looking for any additional feedback folks may have. https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit# Thanks, Sumanth On Tue, May 28, 2019 at

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-29 Thread Kyle Samson
Thank you Nate and Chris for the feedback. It’s a shame this won’t make it through to 4.0 release but I do understand respecting the feature freeze. I just figured I’d chime in as one of the parties Jon mentioned. I will definitely continue to follow the mailing list and feature development. -

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Scott Andreas
Echoing Jon’s point here – JH: “My thinking is I'd like to be able to recommend 4.0.0 as a production ready database for business critical cases” I feel that this is a standard that is both appropriate and achievable, and one I’m legitimately excited about. Re: the current state of the test

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Nate McCall
Hi Kyle, I understand your frustration here - I really do. There are a lot of awesome additions, features, etc. that have been stuck in purgatory for far longer than any of us would like. It will be worth it once we get 4.0 to a stable point as we will be in a much better position to iterate

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Chris Lohfink
I think that was intent but ran out of time. There were 2 approaches to this, one being dumping the Metric's into a virtual table, and another to have specialized views (like nodetool). The later is started in CASSANDRA-14670 and still

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Kyle Samson
Hey all, Thought I’d chime in here as one of the people surprised that virtual tables for table stats weren’t being included in 4.0, especially given that QoL for administrators is one of the 4.0 promises. -Kyle Samson On 2019/05/28 16:39:59, Jon Haddad wrote: > Sept is a pretty long ways

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Dinesh Joshi
+1. Wiki could be useful to document what the overall plan. Jira to track progress. Dinesh > On May 28, 2019, at 10:20 AM, Joshua McKenzie wrote: > >> >> The unofficial rule is to not upgrade to prod till .10 is cut. > > FWIW, I believe it's historically .6. Which is still not a great look

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Jon Haddad
My thinking is I'd like to be able to recommend 4.0.0 as a production ready database for business critical cases of TLP customers. If it's not ready for prod, there's no way I'd vote to release it. The TLP tooling I've mentioned was developed over the last 6 months with the specific goal of

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Joshua McKenzie
> > The unofficial rule is to not upgrade to prod till .10 is cut. FWIW, I believe it's historically .6. Which is still not a great look for the project. There's a ton of work going into testing 4.0 already. While I intuitively and anecdotally (from the people I've backchanneled with) believe

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread sankalp kohli
Hi Jon, When you say 4.0 release, how do u match it with 3.0 minor releases. The unofficial rule is to not upgrade to prod till .10 is cut. Also due to heavy investment in testing, I dont think it will take as long as 3.0 but want to know what is your thinking with this. Thanks,

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Jon Haddad
Sept is a pretty long ways off. I think the ideal case is we can announce 4.0 release at the summit. I'm not putting this as a "do or die" date, and I don't think we need to announce it or make promises. Sticking with "when it's ready" is the right approach, but we need a target, and this is

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-27 Thread Nate McCall
Hi Sumanth, Thank you so much for taking the time to put this together. Cheers, -Nate On Tue, May 28, 2019 at 3:27 AM Sumanth Pasupuleti < sumanth.pasupuleti...@gmail.com> wrote: > I have taken an initial stab at documenting release types and exit criteria > in a google doc, to get us started,

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-27 Thread Sumanth Pasupuleti
I have taken an initial stab at documenting release types and exit criteria in a google doc, to get us started, and to collaborate on. https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit?usp=sharing Thanks, Sumanth On Thu, May 23, 2019 at 12:04 PM Dinesh Joshi

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-23 Thread Dinesh Joshi
Sankalp, Great point. This is the page created for testing. https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+Quality%3A+Components+and+Test+Plans I think we need to define the various release types and the exit criteria for each type of release. Anybody want to take a stab at this or

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-23 Thread sankalp kohli
Hi, Is there a page where it is written what is expected from an alpha, beta, rc and a 4.0 release? Also how are we coming up with Q4 2019 timeline. Is this for alpha, beta, rc or 4.0 release? Thanks, Sankalp On Thu, May 23, 2019 at 11:27 AM Attila Wind wrote: > +1+1+1 I read a blog post

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-23 Thread Attila Wind
+1+1+1 I read a blog post was talking about last sept(?) to freeze features and start extensive testing. Maybe its really time to hit it! :-) Attila Wind http://www.linkedin.com/in/attilaw Mobile: +36 31 7811355 On 2019. 05. 23. 19:30, ajs6f wrote: +1 in the fullest degree. A date that

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-23 Thread ajs6f
+1 in the fullest degree. A date that needs to be changed is still enormously more attractive than no date at all. Adam Soroka > On May 23, 2019, at 12:01 PM, Sumanth Pasupuleti > wrote: > > Having at least a ballpark target on the website will definitely help. +1 > on setting it to Q4 2019

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-23 Thread Sumanth Pasupuleti
Having at least a ballpark target on the website will definitely help. +1 on setting it to Q4 2019 for now. On Thu, May 23, 2019 at 8:52 AM Dinesh Joshi wrote: > +1 on setting a date. > > Dinesh > > > On May 23, 2019, at 11:07 AM, Michael Shuler > wrote: > > > > We've had 4.0 listed as TBD

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-23 Thread Dinesh Joshi
+1 on setting a date. Dinesh > On May 23, 2019, at 11:07 AM, Michael Shuler wrote: > > We've had 4.0 listed as TBD release date for a very long time. > > Yesterday, Alexander Dejanovski got a "when's 4.0 going to release?" question > after his repair talk and he suggested possibly Q4 2019.

"4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-23 Thread Michael Shuler
We've had 4.0 listed as TBD release date for a very long time. Yesterday, Alexander Dejanovski got a "when's 4.0 going to release?" question after his repair talk and he suggested possibly Q4 2019. This morning Nate McCall hinted at possibly being close by ApacheCon Las Vegas in September.