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, but am generally glad to see any contribution that helps us close items in any pre-release milestone. :-) ________________________________________ From: Mick Semb Wever <m...@apache.org> Sent: Tuesday, January 14, 2020 10:27 AM To: dev@cassandra.apache.org Subject: Re: Cassandra 4.0 Dev Work Status > - *Progress: *We've closed out 18 issues > > <https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixversion%20in%20(4.0%2C%204.0.0%2C%204.0-alpha%2C%204.0-beta)%20AND%20resolved%20%3E%3D%20-4w> > in the past 4 weeks of a total of 115 tickets > <https://issues.apache.org/jira/issues/?filter=12347782> across > 4.0-alpha, 4.0-beta, and 4.0. > shouldn't we only have issues closed in 4.0-alpha, given we are not yet at 4.0-beta and 4.0 ? --------------------------------------------------------------------- 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
