Re: FREEZE: All 2.0.x changes require release team confirmation

[Michael Meeks <michael ximian com>]

Hi Jeff,

On Fri, 2002-08-23 at 09:41, Jeff Waugh wrote:
> Today we have a code freeze for the 2.0.x branch, any further changes
> require release team confirmation. String changes also require i18n team
> confirmation.

	I'm highly confused about what you are saying here. Are you asking
people to create a micro branch, to ensure that the 2.0.2 release is
well managed ?

	Or are you saying that Gnome 2.0 is now hard frozen ? and that any
further changes must be approved by Louis as critical bugs, and then the
code approved by the release team before being committed ?

	That would seem unreasonably rash to me; given the existing performance
problems, and prevelance of minor bugs that still need fixing in Gnome
2.0.X especially in some modules.

	To make such a large request of hackers generally, one would assume
that this was discussed in great detail at a release team meeting ? is
there a pointer to the minutes of that somewhere ?

	Or - perhaps are you proposing a different sort of freeze for the 2.0.X
branch, or perhaps a continuation of the current policy.

	Separately but also concerningly do you seriously believe that we won't
have a release beyond 2.0.3 (amazing) ? it seems ironic that while all
this effort goes into trying to get a stable release - it appears to be
proposed that we now impose an intolerable burden on bug fixing in the
stable branch while we rush into unstable development. 

	Surely, a primary goal of the release team, has to be doing the boring
work of ensureing that maintenance, bug fixing and releasing continues
to happen nicely on the stable branch so we don't get a Gnome 1.4.1
again.

	In short - I'm confused, and potentially worried.

	Regards,

		Michael.

-- 
 mmeeks gnu org  <><, Pseudo Engineer, itinerant idiot