Changes between Version 23 and Version 24 of WebKitGTK/Releasing

Timestamp:

Jul 22, 2015 12:13:19 AM (9 years ago)

Author:

Carlos Garcia Campos

Comment:

--

WebKitGTK/Releasing

@@ -1 @@
-= Making a release of WebKit/GTK+ =
-{{{
-#!html
-<div style="width:100%">
-<div style="font-size:30px; background-color: red; font-weight: bold; margin: 0 auto; width: 500px; text-align: center;">The contents of this page are out of date.</div>
-</div>
-}}}
+= Making a release of WebKitGTK+ =
 
 This document describes the steps toward making a release. To understand release strategy and timing please see [https://trac.webkit.org/wiki/WebKitGTKStableReleases]
 
 == 1. The last commit before release ==
-  * Update the NEWS file using the same format as the previous entry.
+  * Update the [https://trac.webkit.org/browser/trunk/Source/WebKit2/gtk/NEWS NEWS] file using the same format as the previous entry.
       * Identify the commit id of the previous release (NEWS file is normally changed only when releasing, so you could get the commit id of the previous release by looking at NEWS history)
       * Summarize major changes briefly in a style similar to other entries in NEWS. 
@@ -16 +10 @@
            * Copy the script to Tools/Scripts and run it giving the commit id of the previous release. 
            * It returns a list of bugs fixed since the given revision that might be related to the GTK port and the list fo people who fixed every bug.
-      * Take special care to note any additions in the API. The following command will show each patch that has changed a public header file since the given version:
-{{{
-$ find Source/WebKit/gtk/webkit/ -name "webkit*.h" ! -name '*private.h' | xargs git log -p <commit-id-of-previous-release>.. --
-}}}
-  * Update Source/autotools/Versions.m4:
+      * Take special care to note any additions in the API. 
+  * Update [https://trac.webkit.org/browser/trunk/Source/cmake/OptionsGTK.cmake Source/cmake/OptionsGTK.cmake]:
     * The public version is controlled by the lines:
         {{{
-m4_define([webkit_major_version], [1])
-m4_define([webkit_minor_version], [7])
-m4_define([webkit_micro_version], [5])
+set(PROJECT_VERSION_MAJOR 2)
+set(PROJECT_VERSION_MINOR 9)
+set(PROJECT_VERSION_MICRO 4)
         }}}
-    * The [http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html libtool library version] is controlled by the line:
-     {{{ m4_define([libwebkitgtk_version], [C:R:A]) }}}
+    * The [http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html libtool library version] is controlled by the lines:
+     {{{  
+CALCULATE_LIBRARY_VERSIONS_FROM_LIBTOOL_TRIPLE(WEBKIT2 C R A)
+CALCULATE_LIBRARY_VERSIONS_FROM_LIBTOOL_TRIPLE(JAVASCRIPTCORE C R A)
+     }}}
         * C (current): increment if the interface has additions, changes, removals.
         * R (revision): increment any time the source changes; set to 0 if you increment CURRENT
         * A (age): increment if any interfaces have been added; set to 0 if any interfaces have been changed or removed. Removal has precedence over adding, so set to 0 if both happened.
-    * The user-agent version should be updated from Source/WebCore/Configurations/Version.xcconfig. It's controlled by the lines:
+    * The user-agent version should be updated from [https://trac.webkit.org/browser/trunk/Source/WebCore/Configurations/Version.xcconfig Source/WebCore/Configurations/Version.xcconfig]. It's controlled by the lines:
     {{{
-m4_define([webkit_user_agent_major_version], [535])
-m4_define([webkit_user_agent_minor_version], [20])
+add_definitions(-DUSER_AGENT_GTK_MAJOR_VERSION=602)
+add_definitions(-DUSER_AGENT_GTK_MINOR_VERSION=1)
     }}}
 
  == 2. Run final tests before release ==
-  * Run `make distcheck` with the [http://thread.gmane.org/gmane.comp.gnu.make.bugs/4219 patched version of gnumake] (or take [http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-devel/make/files/ `make-3.8x-long-cmdline.patch` from here]).
-    * Running "make distcheck" should result in no warnings or errors and show:
+ * Generate the HTML documentation
     {{{
-==================================================
-webkit-X.Y.Z archives ready for distribution:
-webkit-X.Y.Z.tar.xz
-==================================================
-}}}
+WebKitBuild/Release $ ../../Tools/gtk/generate-gtkdoc
+    }}}
+ * Run [https://trac.webkit.org/browser/trunk/Tools/gtk/make-dist.py make-dist.py] script with the -c option to ensure a clean build is done
+    {{{
+WebKitBuild/Release $ export MAKE_ARGS=-j16
+WebKitBuild/Release $ ../../Tools/gtk/make-dist.py -c -s ../../ ./manifest.txt
+    }}}
  * Commit the changes to NEWS and configure.ac. It's especially important to mention the new version number in your commit message. 
  * Check that the bots are not horribly broken and run the layout tests locally and see that they are in reasonably good health
 
 == 3. Make the release ==
- * `make distcheck` should have created tarball in the build directory. Upload it to petibonum.igalia.com. 
- * Update or clone the [https://gitorious.org/webkitgtk/webkitgtkdotorg/ webkitgtkdotorg repository] and run webkit-release script with the new tarball
-{{{
+ * [https://trac.webkit.org/browser/trunk/Tools/gtk/make-dist.py make-dist.py] should have created tarball in the build directory. Compress it with xz:
+    {{{
+WebKitBuild/Release $ xz -f webkitgtk-X.Y.Z.tar
+    }}} 
+ * Update or clone the [https://github.com/WebKitGTK/webkitgtk.org webkitgtk.org repository] and run webkit-release script with the new tarball
+    {{{
 ./webkit-release release --host=<host-to-upload-the-tarball> webkitgtk-X.Y.Z.tar.xz
-}}}
+    }}}
  * Check the commit generated by webkit-release script and push it.
  * Tag the release using the command:
-{{{
+    {{{
 svn cp http://svn.webkit.org/repository/webkit/trunk/  http://svn.webkit.org/repository/webkit/releases/WebKitGTK/webkit-[release version]
-}}}
+    }}}
 
 == 4. After the release ==