Yep that makes sense to me. There's still much work to be done to exercise 4.0 builds to identify unknown issues that haven't yet been filed – but those items can be tagged as release blockers as they're identified. 👍
________________________________________ From: Joshua McKenzie <jmcken...@apache.org> Sent: Saturday, March 28, 2020 7:14 AM To: dev@cassandra.apache.org Subject: Idea: Marking required scope for 4.0 GA vs. optional As we're under a feature freeze but not code freeze, there are quite reasonably tickets being opened for 4.0 (alpha, beta, or rc) that look like nice to haves for the release but wouldn't necessarily block cutting GA. I think there would be value in us flagging tickets that are required for 4.0 to get out the door as blockers - it looks like we don't have the Priority entry anymore (a good thing imo) but we could use the label field to indicate which tickets are blockers and filter our JIRA board and weekly reporting on that. That would also help contributors know where to focus their efforts to help get 4.0 out the door while not stifling people scratching their own itch on things leading up to the release. What do the rest of you on the project think? ~Josh
