Changes between Version 24 and Version 25 of QtWebKitReleases


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

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitReleases

    v24 v25  
    2424== Release branch creation ==
    2525
    26   * Release branches are hosted at http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit
    27   * They're created from the {{{master}}} branch at http://gitorious.org/webkit
    28   * Source packages are created from this branch. See [wiki:"QtWebKitPackaging" QtWebKitPackaging] for details and instructions for producing packages.
     26  * Release branches are hosted at http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit;
     27  * They're created from the {{{master}}} branch at http://gitorious.org/webkit, which is kept in sync with the upstream SVN repository;
     28  * Up to Qt-4.8, packages for integration into Qt are created from the release branch. See [wiki:"QtWebKitPackaging" QtWebKitPackaging] for details and instructions for producing such packages.
    2929
    3030== Getting changes into a release branch ==
     
    3636  * Crashes
    3737  * Broken build
    38   * Regression from the last minor release
     38  * Regression from the previous release
    3939  * Documentation changes
    4040  * Crucial usability issue (after discussion in the mailing list)
     
    4242There are two ways to integrate changes into a release branch:
    4343
    44   * The commit is landed in the trunk and then it is cherry-picked into the release branch.
     44  * The commit is landed in trunk and then cherry-picked into the release branch.
    4545  * Time constraints prevent us from landing the patch and we have to include a change before landing it (exceptional patch, see below).
    4646
     
    5656
    5757After the release we have to make a concentrated effort in reducing the number of exceptional patches, by reviewing the changes in the bugs that the tracker bug ([https://bugs.webkit.org/show_bug.cgi?id=32653 32653]) depends on.
    58 
    5958
    6059== Procedures for cherry-picking and weekly releasing ==
     
    8584Don't forget to tag the repository (and {{{git push --tags}}}) before making an announcement.
    8685
     86== Release Criterias ==
     87
     88These are the simplified release criteria. Q&A criterias and product requirements are not listed here.
     89
     90=== Technology Previews (TPs) ===
     91
     92A 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.
     93
     94 * All buildbots should be green;
     95 * The development team should be relatively confident that basic features work on the reference platform;
     96 * The code builds and pass through a basic [http://en.wikipedia.org/wiki/Smoke_testing smoke test] on all Tier 1 platforms;
     97
     98=== Betas ===
     99
     100A 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.
     101
     102 * We have buildbots running on all Tier 1 platforms and they're green;
     103 * 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);
     104 * 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;
     105 * The code builds and pass through a basic [http://en.wikipedia.org/wiki/Smoke_testing smoke test] on all Tier 2 platforms;
     106
     107=== Release Candidate (RC) ===
     108
     109A RC release is made when we believe the code is ready to ship.
     110
     111 * There has been at least one beta release;
     112 * All buildbots are green;
     113 * There are no critical bugs blocking the release;
     114 * Reports from Q&A indicate we're in better shape than the previous official version;
     115 * We're confident that the software is ready;
     116
     117Once the first RC is out, no more "nice-to-have" fixes will be accepted and thus the meta bug is closed;
     118
     119=== Final Release ===
     120
     121The final release is the last RC but with final versioning.
     122
     123 * At least one week has passed since the last RC release and no critical bugs have been reported;
     124
     125=== Minor Update (maintenance) ===
     126
     127 * Minor versions are released to fix security issues and may include critical bug-fixes;
     128
     129== Supported Platforms ==
     130
     131'''Reference Platform :'''
     132 * Linux Desktop
     133
     134'''Tier 1 :'''
     135 * Apple Mac OS X 10.6 (Cocoa)
     136 * Microsoft Windows XP SP3 32-bit
     137 * Microsoft Windows 7 32 bits
     138 * Symbian (Symbian{{{^}}}3)
     139
     140'''Tier 2 :'''
     141 * Microsoft Windows Vista 32 bits
     142 * Apple Mac OS X 10.5 (Cocoa)
     143 * Meego 1.x
     144
     145See QtWebKitPlatformSupport for the meaning of Tier 1, 2 and Reference Platform.
     146
    87147== Release Management Tools ==
    88148