Changes between Version 17 and Version 18 of QtWebKitRelease22


Ignore:
Timestamp:
May 17, 2011 1:20:15 PM (8 years ago)
Author:
Ademar Reis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitRelease22

    v17 v18  
    77For 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].
    88
    9 == Roadmap ==
     9== Status and Roadmap ==
    1010
    11 Releases are made preferably on Mondays. Week numbers are from the current week when the release is made.
     11Releases are made preferably on Mondays. Week numbers are from the previous week relative to when the release is made.
    1212
    1313The current proposal (still work in progress):
    1414
    15  * Branch from trunk: 2011-05-04 (week 18) '''DONE''': r85855, [http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/commits/qtwebkit-2.2 branch on gitorious]
    16  * First TP: 2011-05-09 (week 19) '''DONE''': [http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/commits/qtwebkit-2.2-tp1 tag on gitorious]
    17  * Beta1: 2011-05-23 (week 21)
    18  * RC1: 2011-06-13 (week 24)
    19  * Release: 2011-06-26 (week 26)
     15 * Branch from trunk: 2011-05-04 (week 17) '''DONE''': r85855, [http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/commits/qtwebkit-2.2 branch on gitorious]
     16 * First TP: 2011-05-09 (week 18) '''DONE''': [http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/commits/qtwebkit-2.2-tp1 tag on gitorious]
     17 * Weekly builds (tags on gitorious):
     18   * qtwebkit-2.2-week19 [https://lists.webkit.org/pipermail/webkit-qt/2011-May/001526.html notes]
     19 * Beta1: late May
     20 * RC1: 2011-06-13 (week 23)
     21 * Release: 2011-06-26 (week 25)
    2022
    2123== Development branch and build instructions ==
     
    2527 * Follow the standard [wiki:QtWebKit#BuildInstructions QtWebKit build instructions] for your platform.
    2628
    27 == Q&A and Release Criteria ==
    28 
    29  * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=55055
    30  * Tracker bug for candidate fixes: https://bugs.webkit.org/show_bug.cgi?id=55056
    31 
    32  * [http://build.webkit.sed.hu/builders/QtWebKit2.2-branch%20x86-32%20Linux%20Release%20Qt%204.7.x Buildbot with Qt-4.7]
    33  * [http://build.webkit.sed.hu/builders/QtWebKit2.2-branch%20x86-32%20Linux%20Release%20Qt%204.8.x Buildbot with Qt-4.8]
    34 
    35 See also QtWebKitCheckList for a weekly basic test procedure on multiple platforms.
    36 
    3729== Supported Platforms ==
    38 
    39 This is a work-in-progress proposal.
     30(work-in-progress)
    4031
    4132'''Reference Platform :'''
     
    4334
    4435'''Tier 1 :'''
    45  * Apple Mac OS X 10.6 (Cocoa)
     36 * Apple Mac OS X 10.6 (Cocoa) -- needs a buildbot with tests
    4637 * Microsoft Windows XP SP3 32-bit -- needs a buildbot with tests
    4738 * Microsoft Windows 7 32 bits -- needs a buildbot with tests
     
    5546See QtWebKitPlatformSupport for the meaning of Tier 1, 2 and Reference Platform.
    5647
     48== Q&A, Trackers and Build bots ==
     49
     50 * Developers perform [wiki:QtWebKitCheckList weekly tests] on the branch on multiple platforms;
     51 * TODO: Q&A team and test procedure;
     52
     53 * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=55055
     54 * Tracker bug for candidate fixes: https://bugs.webkit.org/show_bug.cgi?id=55056
     55
     56 * [http://build.webkit.sed.hu/builders/QtWebKit2.2-branch%20x86-32%20Linux%20Release%20Qt%204.7.x Buildbot with Qt-4.7]
     57 * [http://build.webkit.sed.hu/builders/QtWebKit2.2-branch%20x86-32%20Linux%20Release%20Qt%204.8.x Buildbot with Qt-4.8]
     58
     59== Release Criterias ==
     60
     61These are the simplified, still work-in-progress release criteria. Q&A criterias and product requirements are not listed here.
     62
     63=== Technology Previews (TPs) ===
     64
     65A 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.
     66
     67 * All buildbots should be green;
     68 * The development team should be relatively confident that basic features work on the reference platform;
     69 * The code builds and pass through a basic [http://en.wikipedia.org/wiki/Smoke_testing smoke test] on all Tier 1 platforms;
     70
     71=== Betas ===
     72
     73A 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.
     74
     75 * We have buildbots running on all Tier 1 platforms and they're green;
     76 * The Q&A team has tested the code for regressions against the latest stable release (and bugs have been opened if necessary);
     77 * 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;
     78 * The code builds and pass through a basic [http://en.wikipedia.org/wiki/Smoke_testing smoke test] on all Tier 2 platforms;
     79
     80=== Release Candidate (RC) ===
     81
     82A RC release is made when we believe the code is ready to ship.
     83
     84 * There has been at least one beta release;
     85 * All buildbots are green;
     86 * There are no critical bugs blocking the release;
     87 * We're confident that the software is ready;
     88
     89Once the first RC is out, no more "nice-to-have" fixes will be accepted and thus the meta bug is closed;
     90
     91=== Final Release ===
     92
     93The final release is the last RC with but with final versioning.
     94
     95 * One week has passed since the last RC release and no critical bugs have been reported;
     96
     97=== Minor Update (maintenance) ===
     98
     99 * Minor versions are released to fix security issues and may include minor bug-fixes;
     100
     101
    57102== See also ==
    58103