Re: API freeze for GNOME 2

On 17Nov2001 01:20PM (-0500), Havoc Pennington wrote:
> Maciej Stachowiak <mjs noisehavoc org> writes: 
> > The Gnome 2.0 release team generally likes the sound of this change
> > and the low level of breakage, but we would like to hear more
> > information. In particular, we'd like to see a bugzilla bug report and
> > hear Sven's opinion of the change.
> Please keep in mind that the release team is not supposed to be
> deciding on the merits of patches in general, just on their merits as
> they relate to the release process. i.e. the issue is whether the
> change messes up the release, and is "important enough" - not whether
> the change is the correct change. The latter is still a maintainer
> issue.

We're not trying to evalueate the merits of the specific change. Just
to be 100% clear, that is not our goal at all.

We're trying to be clear on the answers to the following questions:

* How much breakage/risk is involved in this change?

* What kind of burden will it impose on client code?

* Is this change important enough to be worth the schedule risk`?

* Does this problem really require a change and not just an API
addition to solve?

I don't think we have enough information about these questions just
from Alex's post.

We're not going to ever tell anyone "this change is technically subpar
- you should do it differently" except to suggest additions instead of
changes where feasible.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]