Changes between Version 20 and Version 21 of QtWebKitReleases


Ignore:
Timestamp:
May 9, 2011 10:29:36 AM (8 years ago)
Author:
Ademar Reis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitReleases

    v20 v21  
    77== Release branches and their status ==
    88
    9 === QtWebKit 2.0 ===
     9=== QtWebKit 2.2 ===
    1010
    11 '''Status''': released, maintainance
     11'''Status''': branch open, under stabilization
    1212
    13  * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=35784
    14  * [http://trac.webkit.org/wiki/QtWebKitTableOfFeatures20 Internal Release Notes]
    15 
    16 === QtWebKit 2.1 ===
    17 
    18 '''Status''': open, frozen (critical fixes only)
    19 
    20  * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=39121
    21  * Tracker bug for candidate fixes: https://bugs.webkit.org/show_bug.cgi?id=44677
    22  * [wiki:QtWebKitRelease21 QtWebKit 2.1 Release Page]
    23  * [http://trac.webkit.org/wiki/QtWebKitFeatures21 Internal Release Notes]
     13 * [wiki:QtWebKitRelease22 QtWebKit 2.2 Release Page]
     14 * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=55055
     15 * Tracker bug for candidate fixes: https://bugs.webkit.org/show_bug.cgi?id=55056
     16 * [http://trac.webkit.org/wiki/QtWebKitFeatures22 Internal Release Notes]
    2417
    2518=== QtWebKit 2.1.x ===
     
    2821
    2922 * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=50925
    30  * Tracker bug for candidate fixes: https://bugs.webkit.org/show_bug.cgi?id=50926
     23 * [wiki:QtWebKitRelease21 QtWebKit 2.1 Release Page]
    3124
    32 === QtWebKit 2.2 ===
     25=== QtWebKit 2.1 ===
    3326
    34 '''Status''': not branched yet (work is happening on trunk)
     27'''Status''': [https://lists.webkit.org/pipermail/webkit-qt/2011-April/001429.html 2.1.0 released on Apr 18, 2011]
    3528
    36  * Tracker bug for critical fixes: https://bugs.webkit.org/show_bug.cgi?id=55055
    37  * Tracker bug for candidate fixes: https://bugs.webkit.org/show_bug.cgi?id=55056
    38  * [wiki:QtWebKitRelease22 QtWebKit 2.2 Release Page]
    39  * [http://trac.webkit.org/wiki/QtWebKitFeatures22 Internal Release Notes]
     29 * [wiki:QtWebKitRelease21 QtWebKit 2.1 Release Page]
     30 * [http://trac.webkit.org/wiki/QtWebKitFeatures21 Internal Release Notes]
     31
     32=== QtWebKit 2.0 ===
     33
     34'''Status''': 2.0.0 released as part of Qt-4.7, maintenance
     35
     36 * Tracker bug for candidate fixes (maintenance): https://bugs.webkit.org/show_bug.cgi?id=35784
     37 * [http://trac.webkit.org/wiki/QtWebKitTableOfFeatures20 Internal Release Notes]
    4038
    4139== Release branch creation ==
     
    7371After 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.
    7472
     73
    7574== Procedures for cherry-picking and weekly releasing ==
    7675
     
    10099Don't forget to tag the repository (and {{{git push --tags}}}) before making an announcement.
    101100
    102 == Proposal for release testing ==
    103 
    104 The idea for a new release would be that it has no regressions over the previous release. This should mean:
    105 
    106    * All LayoutTests that passed on the old version should pass on the release candidate.
    107 
    108       This can be realized by either storing the list of tests ran on the old release somewhere or using the LayoutTests/ directory of the old release. This has the possible problem that DRT was changed in a incompatible way or the WebKit behavior was changed and now a test would fail. Alternatively one could compare the list of tests that were ran and for every removed test it may not be in the Skipped list.
    109 
    110    * It should pass all manual tests.
    111       This can be realized by creating a "meta" manual page linking to all manual tests we want to run before the release.
    112 
    113    * It should not consume more memory on the existing test cases and benchmarks.
    114       This can be realized by using libmemusage.so and use QtLauncher on a list of URLs and use mirrored content (from the benchmarking). Afterwards one can manually compare the memory usage.
    115 
    116     * Survive a night with iexploder or other fuzzing utilities.
    117 
    118 As part of the release the tester(s) should write a simple protocol. It should include the LayoutTests ran, the manual tests ran and their results, the result of libmemusage.so and should be stored on a publicly available place for future reference.
    119 
    120 == Nokia Releases ==
    121 
    122 Nokia creates the following official releases of QtWebKit:
    123 
    124    1. Every releases consists of a source package that is available for download (todo: add location). The source package can be compiled and installed into an existing installation of Qt, as an convenient way for developers to try out new releases with their applications.
    125    1. QtWebKit releases are included in the Qt application and UI framework and can be downloaded as source and binaries from http://qt.nokia.com/. Qt's support team provides commercial support for these releases.
    126    1. Nokia also delivers the QtWebKit releases to the Symbian Foundation and the Maemo project.
    127 
    128 In these release channels the release is always first available as a source only package. New releases will be included in future versions of Qt. It may happen that a release becomes available in Symbian or Maemo before it is included in Qt, as these delivery channels are independent. The inclusion of newer QtWebKit releases in Symbian and Maemo and their availability as separate source packages constitutes the independence from Qt.
    129 
    130 We maintain backwards binary and source compatibility between minor and patch releases.
    131 
    132101== Release Management Tools ==
    133102