Re: [gtkmm] Questions and information

[Chris Vine <chris cvine freeserve co uk>]

On Monday 23 June 2003 9:29 am, Murray Cumming Comneon com wrote:

> No, stable API branches are not affected by unstable branches. Unstable
> branches stabilise when ready. You would be best to discuss practical
> problems with this policy if you think any exist.

Sure, provided that it does not result in a flame-fest, and that politeness 
can be maintained.

I think gtkmm should keep step with the Gtk+/gnome policy on API breakage (ie, 
none in version 2.*).  I believe that is the approach that a library which 
was aimed at the end user and intended for adoption by large projects would 
do: it is the policy which proprietary toolkits (with which you compared 
gtkmm in a favourable light) would adopt.  Gtk+ has adopted this policy for 
the explicit purpose of encouraging more widespread adoption.

If this policy were adopted, there might also then be a chance that gtkmm will 
be shipped with Redhat and Suse (when I last looked, Redhat had dropped it 
entirely, and Suse were shipping only version 1.2, but it is about two or 
three months since I last looked, so this may have changed).

Chris.