Consolidating the various freezes

Martin Pitt martin.pitt at
Mon Sep 17 07:11:38 BST 2007

Hi Matthew,

Matthew East [2007-09-15 13:59 +0100]:
> > On Fri, Sep 14, 2007 at 05:30:40PM +0200, Martin Pitt wrote:
> > > Documentation might need its own (later) string freeze to allow
> > > translators to catch up, but that's a different level IMHO.
> I'm not sure what is meant by a different level. If you mean that we
> should establish a freeze which is later than the proposed UI freeze,
> but that it shouldn't be on the ReleaseSchedule page, I don't really
> agree: a freeze is a freeze.

I meant that I don't see the purpose of freezing the actual distro and
the documentation UI/strings at the same time. After all, the purpose of
the distro UI freeze is to provide a fixed target, so that the doc
team can start updating/writing documentation for that release until
the doc string freeze is reached (from then on, doc translators have a
fixed target).

I do think that the DocumentationStringFreeze should be on the
ReleaseSchedule page. It hasn't been so far, because this concept
hasn't been in the wiki explicitly so far.

> I'd quite like to develop the idea that we could have a notification
> period which begins before the UI freeze, in which significant changes
> which might affect documentation are reported to the docteam. 

Would certainly be nice, but very hard to implement AFAICS. After all,
we inherit most of the relevant UI from upstreams. Those notifications
should be sent after the distro UI freeze, of course.



Martin Pitt
Ubuntu Developer
Debian Developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 

More information about the ubuntu-devel mailing list