Qt 5.5.0 Post Mortem: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(suggest clarity on toolchain)
No edit summary
Line 4: Line 4:
* Header diffs should be done earlier
* Header diffs should be done earlier
** Perhaps we should do header reviews before the beta (as well as later) in order to catch problems early and avoid trying to address them in a rush.
** Perhaps we should do header reviews before the beta (as well as later) in order to catch problems early and avoid trying to address them in a rush.
* We have a ChangeLog for the Qt modules, but not for the installers. Such a detailed list would help verifying the packages.


== What was causing the delays & how we could improve those ==
== What was causing the delays & how we could improve those ==
Line 10: Line 11:


== What went well & what should be continued ==
== What went well & what should be continued ==
*


== Something else ==
== Something else ==
* Be very vocal and clear about intended support for compilers and toolchains
* Be very vocal and clear about intended support for compilers and toolchains

Revision as of 11:26, 30 June 2015

What needs to be improved & how

  • API Reviews & process
    • There were lots of discussion & changes related to public APIs very late of releasing process. That needs to be improved for the future releases so that API reviews are done early enough & official header diff is just a final verification
  • Header diffs should be done earlier
    • Perhaps we should do header reviews before the beta (as well as later) in order to catch problems early and avoid trying to address them in a rush.
  • We have a ChangeLog for the Qt modules, but not for the installers. Such a detailed list would help verifying the packages.

What was causing the delays & how we could improve those

  • CI system instability
  • We should be able to release extra betas if there are blockers delaying a proper RC. There should never be more than a month between releases once the first beta is out.

What went well & what should be continued

Something else

  • Be very vocal and clear about intended support for compilers and toolchains