Re: String/UI freeze and crying wolf
- From: Gregory Leblanc <gleblanc linuxweasel com>
- To: Stanislav Visnovsky <visnovsky nenya ms mff cuni cz>
- Cc: Kjartan Maraas <kmaraas online no>,GNOME i18n list <gnome-i18n gnome org>, gnome-doc-list gnome org,desktop-devel gnome org
- Subject: Re: String/UI freeze and crying wolf
- Date: 27 May 2002 11:02:47 -0700
On Mon, 2002-05-27 at 08:41, Stanislav Visnovsky wrote:
> On 24 May 2002, Kjartan Maraas wrote:
> > - Discuss other possible ways to handle this
> > Please let us know what you think about this. What should be done now,
> > what can be done long term to make the process more streamlined and how
> > to make lives easier for both the translation/docs camps and the
> > developer/release team camps.
> 1. dotPlan is not clear.
> - remove old schedules and left only the current one (I mean remove or
> hide those horrible "Revised schedule" notes)
I agree this needs to be made into something a lot nicer/easier to
> - markup important freeze dates
> - define the terms (what does UI FREEZE mean = no commits of translatable
> messages without approval of release team or something?)
> - set the last date for translation commits (it is PACKAGE DUE dates?)
I'll try to get some of these done soon.
> 2. Stick to the release plan
> This way we can force developers to stop adding (hidden) features but to
> squash bugs and stop adding new messages. And the release team needs to
> enforce the deadlines.
> 3. I feel we have too many prereleases leading to lowering of their
> importance for developers IMHO. I would suggest 2 betas and 1 release
> candidate as a starting point.
Huh? You think we're releasing code too often? :-) I don't think too
many people agree with that sentiment, though I'm sure there are a few.
Portland, Oregon, USA.
Please don't copy me on replies to the list.
] [Thread Prev