Establish forward plan for Qt5 versioning
The transition from Qt 5.0 to 5.2 in the Ubuntu 14.04 LTS cycle was (and remains, at the time of writing) a long process that was much more drawn-out than many people wanted. Discuss plans for the next cycle and going forward to try to avoid this happening again.
Blueprint information
- Status:
- Not started
- Approver:
- Steve Langasek
- Priority:
- Undefined
- Drafter:
- Timo Jyrinki
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Possible topics for discussion:
* There was a period where the blockers were fairly opaque to some of the stakeholders. This got better in February; can we avoid this happening again?
* What level of pre-landing CI and bug-fixing is appropriate? We seem to have opted for "perfect"; but there's a credible argument that lowering the bar at least a bit would have allowed us to move forward more effectively overall.
* Are the Ubuntu-for-phones and Kubuntu teams collaborating as effectively as they might? In the 14.04 case, both clearly wanted Qt 5.2, but the two teams' ideas of what an appropriate schedule ought to be seemed to be quite different.
* How can we avoid getting to the point where we're landing a substantial new version of Qt after feature freeze again?
* Should the Ubuntu platform fork the Qt packages, so that the Ubuntu client platform does not block community flavors in the future?
http://
