> if any contributor has an opinion which is not technically refuted it will usually be backed by a PMC via a binding -1
clarifying a bit my personal view: if any contributor has an opinion against a proposal (in this case this release proposal) that is not refuted it will usually be backed by a PMC via binding -1 Opinions supporting the proposal are also valuable, provided there are no valid claims against a proposal. On Wed, 29 Nov 2023 at 22:27 Paulo Motta <pa...@apache.org> wrote: > To me, the goal of a beta is to find unknown bugs. If no new bugs are > found during a beta release, then it can be automatically promoted to RC > via re-tagging. Likewise, if no new bugs are found during a RC after X > time, then it can be promoted to final. > > If we end up not releasing a final 5.0 artifact by a Cassandra Summit it > will signal to the community that we’re prioritizing stability and it could > be a good opportunity to get people to test the beta or RC before we stamp > it as production ready. > > WDYT? > > > Aaron (and anybody who takes the time to follow this list, really), > your opinion matters, that's why we discuss it here. > > +1, PMC are just officers who endorse community decisions, so if any > contributor has an opinion which is not technically refuted it will usually > be backed by a PMC via a binding -1 (as seen on this thread) > > On Wed, 29 Nov 2023 at 20:04 Nate McCall <zznat...@gmail.com> wrote: > >> >> >> On Thu, Nov 30, 2023 at 3:28 AM Aleksey Yeshchenko <alek...@apple.com> >> wrote: >> >>> -1 on cutting a beta1 in this state. An alpha2 would be acceptable now, >>> but I’m not sure there is significant value to be had from it. Merge the >>> fixes for outstanding issues listed above, then cut beta1. >>> >> <snip> >> >> Agree with Aleksey. -1 on a beta we know has issues with a top-line new >> feature. >> >> >> >
