It could be a grown pain for the new podlings if they need to go through 10+ voting, but it could make the life more easier by providing some tools to help the podling to find out the issues before sending out the vote. I know it is harder to provide an unify tool which could be useful for all kind of project, but it could address most of common issues if IPMC can build the tools together by sharing our experiences.
Regards, Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jun 17, 2019 at 5:37 PM Justin Mclean <jus...@classsoftware.com> wrote: > > Hi, > > > The biggest fix I’d suggest for the incubator is parallel voting > > Worthy of consideration (please start a thread), but IMO we want to be > careful it doesn’t overwhelm the IPMC. I’ve seen some RCs got through 10+ > votes, and most go through 2 or 3. That’s potentially 2 or 3 or 5x more calls > for votes on the IPMC list, unless we modify it somehow or somehow get more > IPMC members to vote on releases it’s going to need some careful > consideration. > > Some discussion on legal discuss and in the last board report may help reduce > the requirement for revotes like that. > > > after an IPMC vote failed yet again on some aspect that the > > community is not interested in at all (but should be, but still isn’t). > > Or alternatively how could a podling get the community (or it's mentors) to > pick up these things before the IPMC vote? In theory your mentors should pick > up any issues that the IPMC finds, in practise that doesn't always happen. > > Thanks, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
