dbus/doc TODO,1.117,1.118 dbus-specification.xml,1.46,1.47

[Havoc Pennington]

Update of /cvs/dbus/dbus/doc
In directory kemper:/tmp/cvs-serv18232/doc

Modified Files:
	TODO dbus-specification.xml 
Log Message:
2006-11-08  Havoc Pennington  <hp at redhat.com>

	* doc/dbus-specification.xml: add a note about protocol stability

	* doc/TODO: Remove "important for 1.0" section, replace with
	"important for 1.2" section
	


Index: TODO
===================================================================
RCS file: /cvs/dbus/dbus/doc/TODO,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- TODO	8 Nov 2006 23:17:20 -0000	1.117
+++ TODO	9 Nov 2006 00:19:29 -0000	1.118
@@ -1,7 +1,9 @@
-Important for 1.0
+Important for 1.2
 ===
 
- - the spec should say "the protocol will not be changed incompatibly after Month DD, YYYY"
+ - System bus activation
+
+ - Windows port
 
 Important for 1.0 GLib Bindings
 ===

Index: dbus-specification.xml
===================================================================
RCS file: /cvs/dbus/dbus/doc/dbus-specification.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -d -r1.46 -r1.47
--- dbus-specification.xml	7 Nov 2006 06:13:53 -0000	1.46
+++ dbus-specification.xml	9 Nov 2006 00:19:29 -0000	1.47
@@ -138,6 +138,30 @@
       document could use a serious audit to be sure it makes sense to do
       so. Also, they are not capitalized.
     </para>
+
+    <sect2 id="stability">
+      <title>Protocol and Specification Stability</title>
+      <para>
+        The D-Bus protocol is frozen (only compatible extensions are allowed) as
+        of November 8, 2006.  However, this specification could still use a fair
+        bit of work to make interoperable reimplementation possible without
+        reference to the D-Bus reference implementation. Thus, this
+        specification is not marked 1.0. To mark it 1.0, we'd like to see
+        someone invest significant effort in clarifying the specification
+        language, and growing the specification to cover more aspects of the
+        reference implementation's behavior.
+      </para>
+      <para>
+        Until this work is complete, any attempt to reimplement D-Bus will 
+        probably require looking at the reference implementation and/or asking
+        questions on the D-Bus mailing list about intended behavior. 
+        Questions on the list are very welcome.
+      </para>
+      <para>
+        Nonetheless, this document should be a useful starting point and is 
+        to our knowledge accurate, though incomplete.
+      </para>
+    </sect2>
     
   </sect1>