diff options
| -rw-r--r-- | ChangeLog | 7 | ||||
| -rw-r--r-- | doc/TODO | 6 | ||||
| -rw-r--r-- | doc/dbus-specification.xml | 24 | 
3 files changed, 35 insertions, 2 deletions
| @@ -2,6 +2,13 @@  	* Released 1.0.0 +2006-11-08  Havoc Pennington  <hp@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 +	  2006-11-08  John (J5) Palmieri  <johnp@redhat.com>  	* README: remove some of the out of date flags @@ -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  === diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index e1b02f38..986bada4 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -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> | 
