Re: API freeze and feature freeze on Jan 10th
- From: Murray Cumming <murrayc murrayc com>
- To: Bastien Nocera <hadess hadess net>
- Cc: gnome-release-team <release-team gnome org>, "desktop-devel-list gnome org" <desktop-devel-list gnome org>
- Subject: Re: API freeze and feature freeze on Jan 10th
- Date: Sat, 08 Jan 2005 12:02:37 +0100
On Wed, 2005-01-05 at 16:34 +0100, Murray Cumming wrote:
> On Wed, 2005-01-05 at 11:31 +0000, Bastien Nocera wrote:
> > On Wed, 2005-01-05 at 12:21 +0100, Murray Cumming wrote:
> > > On Wed, 2005-01-05 at 11:14 +0000, Bastien Nocera wrote:
> > > > Just to note that the API freeze will leave nautilus-cd-burner in a bad
> > > > state. I haven't had time to finish the work I started on it, and the
> > > > API is still a bit in motion.
> > >
> > > What new API has been (or will be) added/changed?
> > >
> > > What are the consequences of using the older API? Maybe it can wait for
> > > 2.11/2.11?
> >
> > There's no older API, we renamed everything to be namespaced. There are
> > unfinished APIs (like nautilus_burn_recorder_blank_disc()).
>
> Does this mean that reverting to an older version means reverting to
> nautilus 2.8? Is there any way to punt this to GNOME 2.11/2.12 without
> regressions?
>
> Is nautilus-cd-burner used by anything other than nautilus in GNOME
> 2.10? If not, then a slightly-delayed freeze of the nautilus-cd-burner
> API would not have much disadvantage. This would fit in with our regular
> API-freeze-break process.
>
> But I'd like to avoid delaying the API freeze for everything else. Just
> my opinion though.
So, does it seem like nautilus-cd-burner still needs special
consideration for the feature-freeze on the 10th? If yes, what are those
features?
--
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]