Re: Cassandra 4.0 Dev Work Status

Just realized I'd misunderstood Mick's original email, apologies. I'd originally interpreted it as a question of prioritization, but the intent was to ensure that the Fix Version field reflects the release a given change is /included in/, not /originally targeted for/. Apologies for my misunders

Re: Cassandra 4.0 Dev Work Status

> 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

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. In principle I'd interpret work targeting earlier milestones as higher priority, b

Re: Cassandra 4.0 Dev Work Status

>- *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

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

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