We all want an issue free release. The rule that Josh has referenced does not appear to be open to interpretation. Ultimately, it comes down to those who enforce the rules. If all the incubator mentors say they will not be raising issue an issue with this we should move forward.
On Sun., May 22, 2022, 12:50 a.m. Ning Wang, <[email protected]> wrote: > it is a little hard for me to tell if it is a blocker or not. > > "Good catch fixing tgese before the VOTE goes to general helps with the > heron graduation case" > > I think we just need +1 votes from us (unbinded) and mentors (binded). > > On Sat, May 21, 2022 at 4:18 PM Nicholas Nezis <[email protected]> > wrote: > > > As the current release manager, I haven't actually canceled the prior > vote. > > I'm ok cancelling the release based on the feedback, but I didn't think > it > > was drastic enough issues to cancel and redo. It sounded like Dave was > of a > > similar mindset stating that the issues were not blockers. > > > > If you feel strongly that it needs to be addressed, especially if this > > release is somehow tied to graduation out of incubation, the fixes will > > need to be applied to the release branch. I perhaps incorrectly assumed > > that the fixes on the main branch was sufficient for graduation, and > didn't > > need to block this release. > > > > If we want to redo all of the manual build processes, I might be able to > > get to it sometime after next weekend. If we want it earlier, I'm ok > > passing off the release manager duties for someone to do rc3. > > > > Also who are the PMC members who need to vote on the release? Have we > > gotten any engagement? Perhaps Dave can help us with this? > > > > On Fri, May 20, 2022 at 11:09 PM Josh Fischer <[email protected]> > wrote: > > > > > Do we have an expected timeframe to get rc3 out? Anything anyone can > > help > > > with ? > > > > > > -- > > > Sent from A Mobile Device > > > > > >
