** Changed in: qtfeedback-opensource-src (Ubuntu)
Status: New = Fix Released
** Changed in: qt3d-opensource-src (Ubuntu)
Status: New = Fix Released
** Changed in: qtpim-opensource-src (Ubuntu)
Status: New = Fix Released
** Changed in: qtbase-opensource-src (Ubuntu)
** Changed in: qtimageformats-opensource-src (Ubuntu)
Status: New = Fix Released
** Changed in: qtserialport-opensource-src (Ubuntu)
Status: New = Fix Released
** Changed in: qtlocation-opensource-src (Ubuntu)
Status: New = Fix Released
** Changed in:
This week is seeing great progress, and the ETA would be now set to
March 6th, if the FFe is accepted.
The following remaining issues have been fixed or about to be fixed:
- qtvideo-node has been fixed, a manual upload to PPA done while merge is
pending
- qtmultimedia-opensource-src-touch has a
From a release standpoint, the hurdles put in place of this upload via
the CI process exceed anything the release team would normally require
for such an FFe. And considering the Ubuntu phone image is currently
the predominant consumer of Qt5, there's no reason to be concerned that
the CI testing
Dmitry: The relevant blockers are autopilot test failures and multimedia
on Ubuntu Touch. Some manual autopilot testing with phablet-test-run and
Nexus 4 can be seen at http://is.gd/JA1jg1. The latest news on
multimedia was that they know what needs to be done, but I don't have
the latest update
Hi Timo, which of the blockers are still relevant? When do you expect it
to be ready?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278329
Title:
[FFe] Qt 5.2
To manage notifications about this
I know this it not a workable solution for U. This is the first ever
major upgrade of Qt 5, because the Qt 5.1.1 already didn't happen
despite plans. 5.2 on the other hand is too important to not have. The
Qt 5.3 timeframe is such that we shouldn't delay moving to that in U,
but just bite the
What's blocking this from landing now? This has waited far too long in
my opinion. I'm afraid we have so many rules about the development
release working perfectly now that it's almost impossible to use for
development. This is in Debian Testing already.
--
You received this bug notification
You're correct that development release is now kept releasable each day,
and each daily Ubuntu Touch image should be flawless
(http://ci.ubuntu.com/smokeng/trusty/touch/). The new CI Train
integration does not allow code merges to trunks unless they don't
regress those results.
The effects of the
Starting next cycle, Kubuntu will be a major user of Qt5. Landing the major
Qt5 revision just days before, or maybe even after, feature freeze, is totally
unworkable. I think we're likely not to introduce KDE Frameworks 5 packages
in this development cycle, but to do post-release backports
10 matches
Mail list logo
