Le 16/07/15 18:49, Roman Shaposhnik a écrit : > On Thu, Jul 16, 2015 at 1:47 AM, Emmanuel Lécharny <elecha...@gmail.com> > wrote: >> Le 16/07/15 10:41, Justin Mclean a écrit : >>> Hi, >>> >>>> This vote passes with 4 binding "+1" votes, no "0" notes, and 2 "-1" >>>> binding votes. >>> If you read carefully I think you find there were 3 -1 votes on the binary >>> releases. >> True. I -1 the binary release. Interesting case : should we release if >> we have as many -1 than +1 ? > Personally, I'm disappointed in the podling for not taking > care of feedback that seems really easy to take care of.
I'm not. They are dealing with a zero-day exploit, and it was clearly explained on the private mailing list. That some missing and incorrect N&L were detected after the release has been cut is unfortunate (or fortunate, considering taht it has been detected), but this is know known and will be addressed. IMO, considering that a new release will occur soon, for which patches will be applied to fix those incorrect N&L is good enough to vote this release. I seriously *wish* that all the other Apache projects are as respectful to the requirements regarding N&L, and I must say that, having been through Seb scrutinity (thanks, Seb, btw), my own projects were not perfect despite many releases that have been cut in the past. I find it a but tough to say you are disapointed, because they *have* considered the pros and cons of releasing now vs postponing to get the N&L fixed. > >> I'll change my vote to -0 to avoid sucha dead lock :-) >> >> I expect the groovy podling to cut a release asap that fixes the N&L issues. > That's my strong expectation as well. If we're doing this whole > mentoring thing -- lets do it right. I think they are doing it right, so far. My remark was more for the record than anything else. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
