On Monday, March 25, 2013 16:24:01 Thiago Macieira wrote: > On segunda-feira, 25 de março de 2013 22.46.36, Stephen Kelly wrote: > > On Monday, February 25, 2013 17:12:02 Stephen Kelly wrote: > > > On Monday, February 25, 2013 08:07:48 Thiago Macieira wrote: > > > > It was a matter of timing. Since GCC 4.8 is not released yet, I can't > > > > make > > > > the case for it being a P1. > > > > > > I fully disagree with that :). I think compile fixes for compilers that > > > are > > > not released yet qualify. > > > > > > But what's done is done, and you can disagree with what I think too. > > > > The 'not released' compiler became 'the released compiler', by the way. > > > > So unless d9ff510f02bba63dabe7a081a68296056a89ae4c is cherry-picked to the > > release branch, 5.0.2 will not build with GCC 4.8, right? > > Backport and add one Ossi and/or Sergio to the reviewers list. If there's > still time for the release, it will be applied.
Sorry, I don't have GCC 4.8 to test the result of backporting the patch with. My mail wasn't an attempt to get the fix in, but was to draw attention to the fact that compile fixes even for unreleased compilers should always go in the release branch if applicable there. What happens this time with 5.0.2 and GCC 4.8.0 doesn't matter as much as the 'community understanding' of where to put things like this. I still think that the patch should have been rejected on stable until it was in release instead. Even if 5.0.2 was released before GCC 4.8.0, that would still mean that they would be incompatible. That's a good reason it should have been in the release branch in the first place. Have you changed your mind on that? Why does the release of 4.8.0 change anything? No matter which project was released first, they would always be incompatible as a result of the patch going into stable instead of release. Thanks, -- Stephen Kelly <[email protected]> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
