On 15/03/16 09:54, "Development on behalf of Helio Chissini de Castro" <[email protected] on behalf of [email protected]> wrote:
>I agreed partially with Lars > > >Is too late *now*, and we can wait for a quick 5.6.1, but is not entirely >correct in say that we're not raising this issue from some time. >For us in Fedora this issue been happening for a month, since rc releases and >the bug was opened 10 days ago so the fact that is passed unattended >or the fact that depends indirectly on one person only that understands well >the code is that worries more. It’s been marked as a P2, and that means it immediately drops out of the focus of the release team. After the RC, they are only looking at P0 and P1 bugs. > >5.6.0 is more important than regular releases, as Qt project defined as the >LTS release, and this bug do Qt LTS been unusable for the largest showcase >of Qt which is really a not good presentation. > >And can't take the blame away of us packagers and distros as well, that >treated the bug as something magic that Qt project would discover as critical >and go ahead to fix. Mea culpa too. Agree, the word deadlock in the bug report should have caused some warning bells to ring, at the same time the reporters and packagers should raise critical reports for them to the attention of the release team as quickly as possible. > >So, let's take this as a lesson, and maybe try to make a better 5.6.1 release. Agree. But as said, I hope that we can get a 5.6.1 out within a couple of weeks of 5.6.0. Until then, the packagers can apply the patch that fixes/works around the bug on top of 5.6.0. Cheers, Lars > > >Regards, Helio > >KDE Developer > >Fedora KDE packager > > > >On Tue, Mar 15, 2016 at 9:42 AM, Heikkinen Jani ><[email protected]> wrote: > >Hi! > >Release isn't done yet and so on there isn't tag either yet. It should be >there when release is officially done > >Br, >Jani > >>>-----Original Message----- >>>From: Development [mailto:development- >>>[email protected]] On Behalf Of >>>Konstantin Podsvirov >>>Sent: 14. maaliskuuta 2016 20:12 >>>To: [email protected] >>>Subject: [Development] Fwd: [Interest] Qt 5.6.0 (final) packages available >>> >>>Hello everyone and thank you for the good work! >>> >>>I have a related question. According to this post and the comments: >>> >>>http://blog.qt.io/blog/2016/01/18/qt-charts-2-1-0-release >>> >>>It says that Qt 5.6 gives an open community QtCharts 2.1 and it is wonderful! >>>But... looking at the git tags on >code.qt.io <http://code.qt.io> I don't find the 2.1 release (2.0.1 >>>only). >>>If I'm wrong, correct me. >>>Else tell me who can push the correct tag? >>> >>>14.03.2016, 19:59, "Jan Kundrát" <[email protected]>: >>>> On Monday, 14 March 2016 14:22:42 CET, Heikkinen Jani wrote: >>>>> So please inform me >>>>> immediately if there is something new which is preventing us to >>>>> do the release. >>>> >>>> Do you consider "Plasma5 deadlocks during startup" as a blocker? If so, >>>> https://bugreports.qt.io/browse/QTBUG-51676 . It's a regression in the 5.6 >>>> branch ("5.5 works fine. oldish 5.6 works fine, too"), and Thiago is >>>> currently AFK when it comes to Gerrit reviews. >>>> >>>> Cheers, >>>> Jan >>> >>>-- >>>Regards, >>>Konstantin Podsvirov >>>_______________________________________________ >>>Development mailing list >>>[email protected] >>>http://lists.qt-project.org/mailman/listinfo/development >_______________________________________________ >Development mailing list >[email protected] >http://lists.qt-project.org/mailman/listinfo/development > > > > > > > _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
