I agree with Lars. I removed this from RC1 blocker list and added it to new metatask containing issues which is agreed to be fixed in final (https://bugreports.qt-project.org/browse/QTBUG-35145)
And what comes to that metatask & fixes after RC1: In my opinion we should keep delta between RC1 & final as small as possible and add only those fixes which are really needed to be fixed. All nice to have's are unnecessary risk to break something... I hope we can agree we will stage to release branch only those fixes which are listed in that metatask. And adding/removing items to that metatask should be done by discussing it in releasing list. This means also that we should agree creator & ifw sha's for RC1 as well and change those for final only if there is some issue listed in that metatask fixed. Any comments? Br, Jani > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On > Behalf Of Knoll Lars > Sent: 26. marraskuuta 2013 22:29 > To: Giuseppe D'Angelo; [email protected] > Subject: Re: [Releasing] Meeting minutes: Qt 5.2 release team meeting > 25.11.2013 > > On 26/11/13 16:38, "Giuseppe D'Angelo" <[email protected]> > wrote: > > >Il 26/11/2013 15:55, Salovaara Akseli ha scritto: > >> Qt 5.2 RC1 status: > >> - Connection problems on build system and broken submodule update > >>during weekend > >> - Items currently expected for RC1 are either merged or fix integrating > >> - New packages (available during Tuesday) should have those fixes > >>available and enable then RC1 later this week (Update > >>26.11.:http://lists.qt-project.org/pipermail/development/2013- > November/01 > >>4288.html ) > >> - Some recent change broke the qml2puppet builds on Linux. Fix > >>available but doesn't require submodule update. > >> -https://codereview.qt-project.org/#change,72149 not a blocker for > RC1 > >> -https://codereview.qt-project.org/#change,72023 not a blocker for > RC1 > >>or final > > > >Howdy, > > > >https://codereview.qt-project.org/#change,72366 is trying to fix a P1 > >(OSX regression), so please > > > >1) review the patch ;-) > >2) evaluate whether it should block RC. > > I¹ll leave it to someone else to review the patch. I don¹t think it should > block the RC, as most apps won¹t be affected by this. But let¹s get the > fix in for the final. > > Lars > > _______________________________________________ > Releasing mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/releasing _______________________________________________ Releasing mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/releasing
