72 hours is a guide. As long as your project community is agreeable you can say "72hrs or 3 +1".
Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Adrian Cole <adrian.f.c...@gmail.com> Sent: Sunday, March 31, 2019 9:26:08 PM To: general@incubator.apache.org Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote I have a related question. In Zipkin (incubating) last release of one of our projects, we had 3 IPMC +1 votes prior to the formal verification vote. Then we basically just waited 72hrs anyway with no additional votes but it didn't matter as we had what we needed (another came later but still) [1] If a project already has 3 IPMC members active verifying and voting.. it might feel a bit tedious to delay a release an additional 3+ days especially if there is no additional feedback. Not sure the answer here, but I hope the situation is relevant to the thread. For example, should same rules apply when there are no additional IPMC votes needed from what is carried over from the podling vote? -A [1] https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F6e26ccaecba70a5cde1f808d82499701562f370441067b96ca65f09a%40%253Cgeneral.incubator.apache.org%253E&data=02%7C01%7C%7Cf3f98ab49c294fdee58408d6b65a22eb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636896895573897795&sdata=oQg4R6ms2IRkfoGdVAf54vUrhXLaq9DIbmk%2F4SzwTvE%3D&reserved=0 On Mon, Apr 1, 2019, 11:15 AM Ross Gardler <rgard...@outlook.com> wrote: > Just like so many things, this is how it used to be. In fact, back in the > day the only time the IPMC was asked to vote was when there were not enough > mentor votes. > > If you look at all the podlinga I've mentored I have only ever asked for > an IPMC vote on two occasions (that I recall). One because I had absent > mentors (the project never graduated due to lack of success as a community) > and one because it was a very large and complex code base and we asked for > extra eyes on the first release. > > Every other time the community worked with mentors. Once we had the votes > we notified the IPMC that the vote had passed and moved on. > > Requiring an IPMC vote is akin to the board voting on all TLP releases. It > should be stopped. The IPMC are facilitators not gate keepers. > > Individual IPMC members can join the podling communities if they wish to > participate. Why are podlings and mentors answering to the IPMC by default? > > I know the standard answer is because mentors sometimes get too busy. > Sure. If it happens every release is a problem and having to ask for an > IPMC vote highlights the problem. > > I realize this proposal does not go this far, I'm +0 for the proposal as a > step in the right direction, but it doesn't go far enough in my opinion. > > Ross > > Get Outlook for > Android<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7C%7Cf3f98ab49c294fdee58408d6b65a22eb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636896895573897795&sdata=pXkL0wr7fNysnARTzfPwP9pLFRmeJdpIQxFo8Y5Vyuo%3D&reserved=0> > > ________________________________ > From: Craig Russell <apache....@gmail.com> > Sent: Sunday, March 31, 2019 8:30:35 PM > To: Incubator > Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking > IPMC to vote > > This is a proposal to recommend that all Mentors SHOULD vote on podling > releases prior to sending the release for a vote to the IPMC. > > This is not a MUST, since there are many good reasons why a mentor might > be unable to perform the checks needed to vote. We are volunteers after all. > > But if this proposal is adopted, it will minimize the occurrences of a > podling desperately asking for someone, anyone, on the IPMC to please vote. > > It should also minimize the number of podling releases that are shot down > in the full IPMC vote because of something that a Mentor is likely to catch. > > Thanks for your consideration, > > Craig > > Craig L Russell > c...@apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
