Re: Feature Freeze Break or Not Questions

My personal belief is that freeze is more guideline than hard rule,
mostly imposed by the requirement that things be stable when we ship,
and the assumption of limited/boredom-prone bugfixing resources. If
your people are willing to commit that all these things be stable when
we ship, and you think you have the resources to do that and fix your
other bugs, then I say go for it. Of course, if these things are
broken at .0 time, then I'll never cut anyone slack ever again ;)


On Mon, 24 Jan 2005 18:47:51 -0500, JP Rosevear <jpr novell com> wrote:
> I had originally thought that the following Evolution changes did not
> break feature freeze, but now I'm not so sure:
> 1) Exchange personal addressbook offline support
> -caught during our feature review, we already had support for online
> offline mail, calendar and global addressbook (all added before feature
> freeze) but somehow we missed personal address books, it was intended
> but the code didn't actually drop in
> 2) GroupWise Send Status Viewing
> -also caught during our feature review, we had ways to set the options
> for tracking the status but through an oversight the information wasn't
> available to the user via a contextual menu
> 3) RTL Editing in the composer
> -we have RTL viewing in now (before feature freeze), and I had been
> considering any RTL work as more i18n work rather than feature work, but
> I've second guessed myself and would like a second opinion.
> 1) and 2) are in the tarball I'm building for UI freeze.
> -JP
> --
> JP Rosevear <jpr novell com>
> Novell, Inc.
> _______________________________________________
> release-team mailing list
> release-team gnome org

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