Re: Preliminary Gnome 2.14 Schedule

[Elijah Newren <newren gmail com>]

Sorry for the slow response...

On 9/14/05, Danilo Šegan <danilo gnome org> wrote:
> Today at 7:42, Elijah Newren wrote:
> 
> > The specific solutions I'm proposing are:
> >
> >   - Tarballs are due by 23:59 UTC on the Monday specified
> 
> Can we also add a general guideline as to *earliest* when tarballs
> should be rolled out?  I know we can't be too strict on this one
> (every now and then there will be a couple of exceptions; for some we
> will be using very old tarballs such as previous Gnome releases), but
> I believe documentation and translation projects would benefit from
> having exact date until they can work on something while being sure
> that their work will end up in the release.
<snip>
> Asking for a simple "notify gnome-i18n, gnome-doc-list if you are
> releasing early" (just like Rich did with gcalctool in this round)
> would be a great help as well.

I like the general idea of this, but I'm worried about adding too many
strict deadlines all at once.  Also, we may find the
too-early-to-release time needs to be adjusted (e.g. 3 days instead of
2 or whatever) after we've tried it out.  And, well...we currently
don't have a way of flagging release-too-early modules, just
release-too-late ones.  ;-)

How about we make it a non-binding guideline[1] for 2.14 (which
appears at the end of the release-dates page as a reminder), and then
make it a little more strict for the next cycle after we've tried it
out and have a better idea what the right timing is (and have some
scripts and stuff to assist with it)?  Sound reasonable?

Thanks,
Elijah

[1] Basically meaning that we can still contact module authors that
don't follow it and ask them nicely if they'll be able to notify the
right people and/or release within the right window in the future. 
This is different from the strict release-too-late deadline where
modules that miss it can be appear on public
didn't-make-the-deadline-and-were-not-included-in-the-specific-release
list.