Changes between Initial Version and Version 1 of QtWebKitReleases


Ignore:
Timestamp:
Dec 17, 2009 4:41:40 AM (14 years ago)
Author:
Simon Hausmann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitReleases

    v1 v1  
     1
     2= Procedures and policies for releases of QtWebKit =
     3
     4Releases of QtWebKit are cut from WebKit's trunk. Some time before the release a new branch is created and hosted in a Git repository. After the release it becomes a maintenance branch.
     5
     6== Release branch creation ==
     7
     8  * The release branch is hosted at http://gitorious.org/+qtwebkit-developers/webkit/qtwebkit
     9  * It is created off the {{{master}}} branch at http://gitorious.org/webkit
     10  * Extra patches can be included in this branch
     11  * Source packages are created from this branch.
     12
     13== Getting changes into the release branch ==
     14
     15After the release branch has been created there are two ways to integrate changes:
     16
     17  * The commit is landed in the trunk and then it is cherry-picked into the release branch.
     18  * Time constraints prevent us from landing the patch and we have to include a change before landing it (exceptional patch).
     19
     20Exceptional patches must satisfy the following criteria before they are included in the release:
     21
     22  * An entry with the attached patch is filed in bugs.webkit.org (using http://webkit.org/new-qtwebkit-bug ).
     23  * The entry is made dependent on the current tracker bug for patches pending trunk inclusion: https://bugs.webkit.org/show_bug.cgi?id=32653 .
     24  * The patch has a ChangeLog entry.
     25  * Patches that affect the API need to have a unit test included.
     26  * Patches that affect WebCore should have a layout test included, although this is not mandatory.
     27  * At least one WebKit reviewer signs off on the patch and no other reviewer objects.
     28  * The bug is linked from it's corresponding JIRA item at http://bugreports.qt.nokia.com/browse/QTWEBKIT
     29
     30== Cherry-picking changes into the release branch ==
     31
     32If you'd like to include a patch in the release branch, please consider only fixes that
     33
     34    * fix data corruption
     35    * fix crashes
     36    * fixes a previously broken build
     37    * regression from the last minor release
     38    * documentation changes
     39    * crucial usability issue (after discussion the mailing list)
     40
     41The separate [wiki:"QtWebKitBackportingFixes" Backporting Fixes] page tracks the changes to include, both changes from the trunk as well as exceptional patches.