Changes between Version 8 and Version 9 of WebKitGTK/AddingNewWebKit2API

Timestamp:

Mar 21, 2013, 12:23:00 PM (12 years ago)

Author:

Carlos Garcia Campos

Comment:

--

WebKitGTK/AddingNewWebKit2API

@@ -1 +1 @@
 = Adding new API to WebKit2 GTK+ =
 
-{{{
-#!comment
-* Patches including new public API should be approved by at least two reviewers
-Remove this comment when we release the first stable verion
-}}}
+ * Patches including new public API should be approved by at least two reviewers
  * Patches should include API documentation for new methods, properties, signals, etc.
   * See http://developer.gnome.org/gtk-doc-manual/stable/
@@ -13 +9 @@
   * If the patch adds a new public class, add the get_type() method to file [http://trac.webkit.org/browser/trunk/Source/WebKit2/UIProcess/API/gtk/docs/webkit2gtk.types UIProcess/API/gtk/docs/webkit2gtk.types]
   * If the patch adds a new section, remember to update the file [http://trac.webkit.org/browser/trunk/Source/WebKit2/UIProcess/API/gtk/docs/webkit2gtk-docs.sgml UIProcess/API/gtk/docs/webkit2gtk-docs.sgml] too
+  * Add Since: tag using the next major release.
+  * Check if this is the first new symbol for the next major stable release and add the index of new symbols to the file [http://trac.webkit.org/browser/trunk/Source/WebKit2/UIProcess/API/gtk/docs/webkit2gtk-docs.sgml UIProcess/API/gtk/docs/webkit2gtk-docs.sgml]
+  {{{
+<index id="api-index-2-2" role="2.2">
+  <title>Index of new symbols in 2.2</title>
+  <xi:include href="xml/api-index-2.2.xml"><xi:fallback /></xi:include>
+</index>
+  }}}
  * Patches should always include unit tests for new API when possible
  * If the patch adds a new public header