On Tue, 2005-02-22 at 10:19 -0700, Elijah Newren wrote:
> > i.e. the change has happened, you're going to have to deal with it.
> > I
> > don't think this was neccessarily went against any policy, because we
> > don't have any policy on this other than "libwnck can change its API at
> > any time". I do think, though, that we should have a better policy than
> > that - e.g. that unstable APIs should remain frozen from API freeze time
> > until the next development cycle.
>
> Sounds reasonable to me for future releases. Do we want this to just
> apply to libwnck, or to all unstable APIs in the desktop release? If
> so, we need feedback from others whether this is reasonable and
> whether we want to add this as a rule for being in the gnome-desktop
> release.
Yeah, it'd be for all libraries in the desktop, but not in the platform
- e.g. libgnome-menu would be another one.
Cheers,
Mark.
_______________________________________________
Gnome-accessibility-devel mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
