Re: Cassandra 4.0 Dev Work Status

2020-01-22 Thread Jordan West
; differentiate > > between which alpha/beta/RC build a given change lands in. > > > > Thanks Mick! > > > > – Scott > > > > > > From: Mick Semb Weve

Re: Cassandra 4.0 Dev Work Status

2020-01-15 Thread Benedict Elliott Smith
___ > From: Mick Semb Wever > Sent: Tuesday, January 14, 2020 12:44 PM > To: dev@cassandra.apache.org > Subject: Re: Cassandra 4.0 Dev Work Status > > > > I think the intent of the milestones is meant to indicate that

Re: Cassandra 4.0 Dev Work Status

2020-01-15 Thread Benedict Elliott Smith
> > – Scott > > > From: Mick Semb Wever > Sent: Tuesday, January 14, 2020 12:44 PM > To: dev@cassandra.apache.org > Subject: Re: Cassandra 4.0 Dev Work Status > > > > I think the i

Re: Cassandra 4.0 Dev Work Status

2020-01-15 Thread Joshua McKenzie
gt; – Scott > > > From: Mick Semb Wever > Sent: Tuesday, January 14, 2020 12:44 PM > To: dev@cassandra.apache.org > Subject: Re: Cassandra 4.0 Dev Work Status > > > > I think the intent of the milestones is meant to indicate tha

Re: Cassandra 4.0 Dev Work Status

2020-01-14 Thread Scott Andreas
ree that it would be useful to differentiate between which alpha/beta/RC build a given change lands in. Thanks Mick! – Scott From: Mick Semb Wever Sent: Tuesday, January 14, 2020 12:44 PM To: dev@cassandra.apache.org Subject: Re: Cassandra 4.0 Dev Work Status

Re: Cassandra 4.0 Dev Work Status

2020-01-14 Thread Mick Semb Wever
> I think the intent of the milestones is meant to indicate that > contributors view completion of those items as exit criteria for alpha > / beta / RC; not necessarily that all items will be completed in strict > order. Yeah, though there's a nuance here between the ticket milestone when it

Re: Cassandra 4.0 Dev Work Status

2020-01-14 Thread Scott Andreas
ority, but am generally glad to see any contribution that helps us close items in any pre-release milestone. :-) From: Mick Semb Wever Sent: Tuesday, January 14, 2020 10:27 AM To: dev@cassandra.apache.org Subject: Re: Cassandra 4.0 Dev Work S

Re: Cassandra 4.0 Dev Work Status

2020-01-14 Thread Mick Semb Wever
>- *Progress: *We've closed out 18 issues > > >in the past 4 weeks of a total of 115 tickets >

Re: Cassandra 4.0 Dev Work Status

2020-01-14 Thread Joshua McKenzie
Apparently the formatting on this got straight borked. I may try sending subsequent emails from my personal gmail instead of my @apache address to see if that keeps the rich-text formatting. Sorry for the ugliness. ;) On Tue, Jan 14, 2020 at 10:27 AM Joshua McKenzie wrote: > Hello and welcome to

Cassandra 4.0 Dev Work Status

2020-01-14 Thread Joshua McKenzie
Hello and welcome to our kickoff email about the 4.0 release work status. Structure and contents are fluid; if you'd like to see, or not see, something, please reply and let me know as my goal is purely to help meet the needs of our dev community here. My initial thinking is to send this out weekly