Qt 5.0.0 Release: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
[[Category:Release]]
This is the wiki where we plan to keep the operative information about how we work towards releasing Qt 5.0.0.
This is the wiki where we plan to keep the operative information about how we work towards releasing Qt 5.0.0.


=Regular updates=
= Regular updates =


Status updates for the release will be sent on a weekly basis to the [http://lists.qt.io/mailman/listinfo/releasing release mailinglist] ''[lists.qt.io]''.
Status updates for the release will be sent on a weekly basis to the "release mailinglist":http://lists.qt.io/mailman/listinfo/releasing.


=Backlog=
= Backlog =


The backlog of all issues that people has accepted (open or in progress) to be fixed for Qt 5.0.0 can be found in [https://bugreports.qt.io/secure/IssueNavigator.jspa?mode=hide&requestId=13538 Jira] ''[bugreports.qt.io]''.
The backlog of all issues that people has accepted (open or in progress) to be fixed for Qt 5.0.0 can be found in "Jira":https://bugreports.qt.io/secure/IssueNavigator.jspa?mode=hide&requestId=13538.


Please help us by making sure your tasks are on this list (and that the ones you don’t plan on doing are not). This is done by setting “Fix version = 5.0.0 [beta 2/RC 1/(Next Major Release)], and ensuring that it is open or in progress.
Please help us by making sure your tasks are on this list (and that the ones you don't plan on doing are not). This is done by setting "Fix version = 5.0.0 [beta 2/RC 1/(Next Major Release)]", and ensuring that it is open or in progress.


=Moving towards the final release=
= Moving towards the final release =


==Beta 1==
== Beta 1 ==


[[Qt500beta1KnownIssues|Known issues]]
"Known issues":Qt500beta1KnownIssues


==Beta 2==
== Beta 2 ==


[https://bugreports.qt.io/browse/QTBUG-27319 Blockers] ''[bugreports.qt.io]'' (this list needs to be empty before we release the beta)
"Blockers":https://bugreports.qt.io/browse/QTBUG-27319 (this list needs to be empty before we release the beta)


[[Qt500beta2KnownIssues|Known issues]]
"Known issues":Qt500beta2KnownIssues


==RC 1==
== RC 1 ==


[[Qt500RC1KnownIssues|Known issues]]
"Known issues":Qt500RC1KnownIssues


==RC 2==
== RC 2 ==


* [[Qt500RC2KnownIssues|Known issues]]
* "Known issues":Qt500RC2KnownIssues
* [[Qt500 Bugfixes RC1 vs RC2|Bugs addressed since RC 1]]
* "Bugs addressed since RC 1":Qt500_Bugfixes_RC1_vs_RC2


==Final==
== Final ==


* [[Qt500KnownIssues|Known issues]]
* "Known issues":Qt500KnownIssues
* [[Qt500 Bugfixes RC2 vs Final|Bugs addressed since RC 2]]
* "Bugs addressed since RC 2":Qt500_Bugfixes_RC2_vs_Final


=Releasing team=
= Releasing team =


* Lars Knoll – Qt’s Chief Maintainer
* Lars Knoll - Qt's Chief Maintainer
* Thiago Macieira Qt Maintainer and previously release manager
* Thiago Macieira - Qt Maintainer and previously release manager
* Stephen Kelly Qt Maintainer
* Stephen Kelly - Qt Maintainer
* Sean Harmer the <span class="caps">QNX</span> port and help with OpenGL
* Sean Harmer - the QNX port and help with OpenGL
* Kai Koehne, Tim Jenssen and/or Maurice Kalinowski Qt Creator
* Kai Koehne, Tim Jenssen and/or Maurice Kalinowski - Qt Creator
* Topi Reinio Error Manager
* Topi Reinio - Error Manager
* Iikka Eklund, Akseli‎ Salovaara, Johanna Äijälä and Sergio Ahumada Technical releasing, build and packaging
* Iikka Eklund, Akseli‎ Salovaara, Johanna Äijälä and Sergio Ahumada - Technical releasing, build and packaging
* Katherine Barrios Marketing and communication
* Katherine Barrios - Marketing and communication
* Sinan Tanilkan Release Manager
* Sinan Tanilkan - Release Manager


==Meetings and Go/no-go decisions==
== Meetings and Go/no-go decisions ==


The releasing team will meet weekly on <span class="caps">IRC</span> (qt-releases on Freenode). Closer to the release, it is likely that we will meet once a day.
The releasing team will meet weekly on IRC (qt-releases on Freenode). Closer to the release, it is likely that we will meet once a day.


Before the release can happen, the releasing team will participate in a go/no-go meeting, to agree on the release.
Before the release can happen, the releasing team will participate in a go/no-go meeting, to agree on the release.
===Categories:===
* [[:Category:Release|Release]]

Revision as of 10:05, 24 February 2015


This is the wiki where we plan to keep the operative information about how we work towards releasing Qt 5.0.0.

Regular updates

Status updates for the release will be sent on a weekly basis to the "release mailinglist&quot;:http://lists.qt.io/mailman/listinfo/releasing.

Backlog

The backlog of all issues that people has accepted (open or in progress) to be fixed for Qt 5.0.0 can be found in "Jira&quot;:https://bugreports.qt.io/secure/IssueNavigator.jspa?mode=hide&amp;requestId=13538.

Please help us by making sure your tasks are on this list (and that the ones you don't plan on doing are not). This is done by setting "Fix version = 5.0.0 [beta 2/RC 1/(Next Major Release)]", and ensuring that it is open or in progress.

Moving towards the final release

Beta 1

"Known issues&quot;:Qt500beta1KnownIssues

Beta 2

"Blockers&quot;:https://bugreports.qt.io/browse/QTBUG-27319 (this list needs to be empty before we release the beta)

"Known issues&quot;:Qt500beta2KnownIssues

RC 1

"Known issues&quot;:Qt500RC1KnownIssues

RC 2

  • "Known issues&quot;:Qt500RC2KnownIssues
  • "Bugs addressed since RC 1&quot;:Qt500_Bugfixes_RC1_vs_RC2

Final

  • "Known issues&quot;:Qt500KnownIssues
  • "Bugs addressed since RC 2&quot;:Qt500_Bugfixes_RC2_vs_Final

Releasing team

  • Lars Knoll - Qt's Chief Maintainer
  • Thiago Macieira - Qt Maintainer and previously release manager
  • Stephen Kelly - Qt Maintainer
  • Sean Harmer - the QNX port and help with OpenGL
  • Kai Koehne, Tim Jenssen and/or Maurice Kalinowski - Qt Creator
  • Topi Reinio - Error Manager
  • Iikka Eklund, Akseli‎ Salovaara, Johanna Äijälä and Sergio Ahumada - Technical releasing, build and packaging
  • Katherine Barrios - Marketing and communication
  • Sinan Tanilkan - Release Manager

Meetings and Go/no-go decisions

The releasing team will meet weekly on IRC (qt-releases on Freenode). Closer to the release, it is likely that we will meet once a day.

Before the release can happen, the releasing team will participate in a go/no-go meeting, to agree on the release.