Hi, > To the PMC: the next boarding meeting is on 21st April, so we have time to > get this release out and probably more as well (hopefully with the fix > for CASSANDRA-16391) before that date.
If I was a PMC member here, I would reconsider making that release without fixing this issue. I would also discuss on list how previous releases can be corrected and how much effort that might be. This is just a friendly suggestion. > Would you mind switching hats here and also representing the project by > including the following items: > - the project is actively working on addressing the fault, > - the project has taken this approach since incubation², > - no one has mentioned it until now, and in the middle of a release vote > are expecting an impromptu change, > - there is agreement, in the project and on legal³, that the ASF policy > docs are not clear on the matter and needs to be improved, > - the project is very keen to see those docs improved asap so to be > confident of changes they invest in. It good to see you are taking action, but I think the situation is a little more seriously that you may realise, I suggest you look at what actions the board has taken in similar situations in the past. I'll update the board agenda item to reflect the current situation. Thanks, Justin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
