> genuinely feel strongly enough that this is indicative of further problems and another RC will provide us with more time to find similar issues or perhaps just give everyone a sense of confidence in the release.
It's both of those things. Another week isn't going to cost us anything. We don't want to destroy the momentum 7 seems to be gathering in the community ... I think this a good reason to postpone for another week, to inspire confidence in those people responsible for making the decision to adopt ... and possibly good reason to not wait another two weeks. No one is expecting 0.0 or any version to be bug free, but the simplicity of the fix says nothing about the seriousness of the bug. I think it quite serious _because_ we are a few days from GA, had this been found a month ago it wouldn't seem so serious. Pushing ahead like nothing happened doesn't seem smart, pushing ahead at a cautious pace does. Cheers Joe On Mon, Nov 23, 2015 at 11:21 AM, Julien Pauli <jpa...@php.net> wrote: > On Mon, Nov 23, 2015 at 11:17 AM, Rasmus Lerdorf <ras...@lerdorf.com> > wrote: > > On Nov 23, 2015, at 10:35, Derick Rethans <der...@php.net> wrote: > >> > >>> On November 23, 2015 10:08:18 AM GMT+01:00, Rasmus Lerdorf < > ras...@lerdorf.com> wrote: > >>>> On 11/23/2015 09:49 AM, Phil Sturgeon wrote: > >>>> The "There will always be bugs" argument is a strawman, nobody is > >>>> saying wait until it's perfect. > >>>> > >>>> People in this thread are consistently conflating "there will always > >>>> be bugs" with "lets just ignore this bug which is 'around critical' > >>>> and crack on because yolo." > >>> > >>> You seem to be confused Phil. Nobody is arguing that this bug shouldn't > >>> be fixed. The question is all about how severe it is and whether it > >>> should trigger another release candidate. > >> > >> Do I understand that you'd like to release 7.0.0 as 7.0.0RC7 + the > count fix on Thursday? > > > > Yes > > > >> I don't think we should push out 7.0.0 without the count fix, but I > also don't think it warrants another RC. > >> > >> If people think it needs another RC, then perhaps do one on Thu 26th > with just RCA+ count fix, plus final on Thu Dec 3rd? > > > > I am ok with either. I don't think the count fix is destabilizing enough > to warrant another RC. The fix seems simple and localized to me, but either > people are confused, or they genuinely feel strongly enough that this is > indicative of further problems and another RC will provide us with more > time to find similar issues or perhaps just give everyone a sense of > confidence in the release. > > > > There is also the fact that a lot of us are in Paris this week and and > at least some of us will be in transit on the 26th so a one-week delay > might be a good idea for that reason alone. > > I'am balanced. > > We discovered a bug, we have a fix , the fix is easy, self contained, > reviewed by many eyes. > > So, we have all we need for a GA now, this week, no ? > > Pushing another RC is all right, but if we find new bugs in this RC, > some that could be critical, then we'll postpone GA to January, > because we'll then fall in mid-December, etc... > > We all have eyes, we all can spot bugs whenever we want to. Why another RC > now ? > With another RC, we have time to concentrate on the code, OK, but we > still have this time if we are in GA, as we'll have anyway a 7.0.1 > coming shortly after... > > > I'm not really +1 for another RC this week, but better for a GA. But > that's my opinion... > > > Julien.P >
