On Nov 27, 2013, at 3:59 PM, Knoll Lars <[email protected]> wrote:
> > > On 27/11/13 15:03, "Heikkinen Jani" <[email protected]> wrote: >> >> Hi all, >> >> This issue is P0 and so on blocking the RC1 at the moment. There is already >> fix proposals available but those aren’t passing the CI >> >> https://codereview.qt-project.org/#change,72183 : This seems to be real >> failure and fix needed before re-stage >> https://codereview.qt-project.org/#change,72535 : Failure seems to be >> unrelated to change and that’s why re-staged >> >> Because we don’t have these through CI yet it means it will be impossible to >> get packages with these fixes tomorrow morning. If we get these through CI >> soon and after that qt5.git can be integrated without problems it might be >> possible to get packages during tomorrow. But what if we couldn’t get these >> packages tomorrow? I recommend that we release RC1 on Friday and fix issue >> on final. >> > It would be very good to get the fixes in, but I don't believe we should > delay the RC a lot further because of them. The hanging of the render loop > can apparently be worked around by setting the QSG_RENDER_LOOP environment > variable to basic. > But then we'd somehow need to make sure it's being set in the packages for > creator. What side effects would that have? There must be some reason why that isn’t the default ;) Also I have actually very bad feelings regarding releasing on a friday. We had a policy not to do that, what has happened with that? -- Eike Ziller, Senior Software Engineer - Digia, Qt Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Releasing mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/releasing
