Changes between Version 42 and Version 43 of QtWebKitRelease22


Ignore:
Timestamp:
Sep 22, 2011 11:01:18 AM (8 years ago)
Author:
Ademar Reis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitRelease22

    v42 v43  
    6161TODO: clarify platform details (OS version, compiler, etc)
    6262
    63 == Supported Platforms ==
    64 (work-in-progress)
    65 
    66 '''Reference Platform :'''
    67  * Linux Desktop
    68 
    69 '''Tier 1 :'''
    70  * Apple Mac OS X 10.6 (Cocoa)
    71  * Microsoft Windows XP SP3 32-bit
    72  * Microsoft Windows 7 32 bits
    73  * Symbian (Symbian{{{^}}}3)
    74 
    75 '''Tier 2 :'''
    76  * Microsoft Windows Vista 32 bits
    77  * Apple Mac OS X 10.5 (Cocoa)
    78  * Meego 1.x
    79 
    80 See QtWebKitPlatformSupport for the meaning of Tier 1, 2 and Reference Platform.
    81 
    82 == Release Criterias ==
    83 
    84 These are the simplified, still work-in-progress release criteria. Q&A criterias and product requirements are not listed here.
    85 
    86 === Technology Previews (TPs) ===
    87 
    88 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.
    89 
    90  * All buildbots should be green;
    91  * The development team should be relatively confident that basic features work on the reference platform;
    92  * The code builds and pass through a basic [http://en.wikipedia.org/wiki/Smoke_testing smoke test] on all Tier 1 platforms;
    93 
    94 === Betas ===
    95 
    96 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.
    97 
    98  * We have buildbots running on all Tier 1 platforms and they're green;
    99  * The Q&A team has tested the code for regressions against the latest stable release using the same testcases (and bugs have been opened if necessary);
    100  * 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;
    101  * The code builds and pass through a basic [http://en.wikipedia.org/wiki/Smoke_testing smoke test] on all Tier 2 platforms;
    102 
    103 === Release Candidate (RC) ===
    104 
    105 A RC release is made when we believe the code is ready to ship.
    106 
    107  * There has been at least one beta release;
    108  * All buildbots are green;
    109  * There are no critical bugs blocking the release;
    110  * Reports from Q&A indicate we're in better shape than the previous official version;
    111  * We're confident that the software is ready;
    112 
    113 Once the first RC is out, no more "nice-to-have" fixes will be accepted and thus the meta bug is closed;
    114 
    115 === Final Release ===
    116 
    117 The final release is the last RC but with final versioning.
    118 
    119  * At least one week has passed since the last RC release and no critical bugs have been reported;
    120 
    121 === Minor Update (maintenance) ===
    122 
    123  * Minor versions are released to fix security issues and may include critical bug-fixes;
    124 
    12563== See also ==
    12664