Changes between Version 17 and Version 18 of QtWebKitRelease22

Timestamp:

May 17, 2011 1:20:15 PM (13 years ago)

Author:

Ademar Reis

Comment:

--

QtWebKitRelease22

@@ -7 +7 @@
 For a detailed list of features supported by QtWebkit-2.2 and the changes from the previous release, check the [http://trac.webkit.org/wiki/QtWebKitFeatures22 Internal Release Notes].
 
-== Roadmap ==
+== Status and Roadmap ==
 
-Releases are made preferably on Mondays. Week numbers are from the current week when the release is made.
+Releases are made preferably on Mondays. Week numbers are from the previous week relative to when the release is made.
 
 The current proposal (still work in progress):
 
- * Branch from trunk: 2011-05-04 (week 18) '''DONE''': r85855, [http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/commits/qtwebkit-2.2 branch on gitorious]
- * First TP: 2011-05-09 (week 19) '''DONE''': [http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/commits/qtwebkit-2.2-tp1 tag on gitorious]
- * Beta1: 2011-05-23 (week 21)
- * RC1: 2011-06-13 (week 24)
- * Release: 2011-06-26 (week 26)
+ * Branch from trunk: 2011-05-04 (week 17) '''DONE''': r85855, [http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/commits/qtwebkit-2.2 branch on gitorious]
+ * First TP: 2011-05-09 (week 18) '''DONE''': [http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/commits/qtwebkit-2.2-tp1 tag on gitorious]
+ * Weekly builds (tags on gitorious):
+   * qtwebkit-2.2-week19 [https://lists.webkit.org/pipermail/webkit-qt/2011-May/001526.html notes]
+ * Beta1: late May
+ * RC1: 2011-06-13 (week 23)
+ * Release: 2011-06-26 (week 25)
 
 == Development branch and build instructions ==
@@ -25 +27 @@
  * Follow the standard [wiki:QtWebKit#BuildInstructions QtWebKit build instructions] for your platform.
 
-== Q&A and Release Criteria ==
-
- * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=55055
- * Tracker bug for candidate fixes: https://bugs.webkit.org/show_bug.cgi?id=55056
-
- * [http://build.webkit.sed.hu/builders/QtWebKit2.2-branch%20x86-32%20Linux%20Release%20Qt%204.7.x Buildbot with Qt-4.7]
- * [http://build.webkit.sed.hu/builders/QtWebKit2.2-branch%20x86-32%20Linux%20Release%20Qt%204.8.x Buildbot with Qt-4.8]
-
-See also QtWebKitCheckList for a weekly basic test procedure on multiple platforms.
-
 == Supported Platforms ==
-
-This is a work-in-progress proposal.
+(work-in-progress)
 
 '''Reference Platform :'''
@@ -43 +34 @@
 
 '''Tier 1 :'''
- * Apple Mac OS X 10.6 (Cocoa)
+ * Apple Mac OS X 10.6 (Cocoa) -- needs a buildbot with tests
  * Microsoft Windows XP SP3 32-bit -- needs a buildbot with tests
  * Microsoft Windows 7 32 bits -- needs a buildbot with tests
@@ -55 +46 @@
 See QtWebKitPlatformSupport for the meaning of Tier 1, 2 and Reference Platform.
 
+== Q&A, Trackers and Build bots ==
+
+ * Developers perform [wiki:QtWebKitCheckList weekly tests] on the branch on multiple platforms;
+ * TODO: Q&A team and test procedure;
+
+ * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=55055
+ * Tracker bug for candidate fixes: https://bugs.webkit.org/show_bug.cgi?id=55056
+
+ * [http://build.webkit.sed.hu/builders/QtWebKit2.2-branch%20x86-32%20Linux%20Release%20Qt%204.7.x Buildbot with Qt-4.7]
+ * [http://build.webkit.sed.hu/builders/QtWebKit2.2-branch%20x86-32%20Linux%20Release%20Qt%204.8.x Buildbot with Qt-4.8]
+
+== Release Criterias ==
+
+These are the simplified, still work-in-progress release criteria. Q&A criterias and product requirements are not listed here.
+
+=== Technology Previews (TPs) ===
+
+A TP release is basically to invite the community to try out new features and provide some initial feedback. It has no major quality guarantees and the decision about when to release it heavily depends on the feeling from the development team.
+
+ * All buildbots should be green;
+ * The development team should be relatively confident that basic features work on the reference platform;
+ * The code builds and pass through a basic [http://en.wikipedia.org/wiki/Smoke_testing smoke test] on all Tier 1 platforms;
+
+=== Betas ===
+
+A beta release means the software is stabilizing but has known bugs we plan to fix before the release. There may be multiple betas during the development process.
+
+ * We have buildbots running on all Tier 1 platforms and they're green;
+ * The Q&A team has tested the code for regressions against the latest stable release (and bugs have been opened if necessary);
+ * Q&A Team is actively testing the release on Tier 1 platforms and the weekly ratio between critical bugs fixed and critical bugs reported is bigger than 1;
+ * The code builds and pass through a basic [http://en.wikipedia.org/wiki/Smoke_testing smoke test] on all Tier 2 platforms;
+
+=== Release Candidate (RC) ===
+
+A RC release is made when we believe the code is ready to ship.
+
+ * There has been at least one beta release;
+ * All buildbots are green;
+ * There are no critical bugs blocking the release;
+ * We're confident that the software is ready;
+
+Once the first RC is out, no more "nice-to-have" fixes will be accepted and thus the meta bug is closed;
+
+=== Final Release ===
+
+The final release is the last RC with but with final versioning.
+
+ * One week has passed since the last RC release and no critical bugs have been reported;
+
+=== Minor Update (maintenance) ===
+
+ * Minor versions are released to fix security issues and may include minor bug-fixes;
+
+
 == See also ==