Formalising a Release Schedule for Docs

[Matthew East]

Hi Phil,

On Wed, Nov 4, 2009 at 12:55 PM, Phil Bull <philbull at gmail.com> wrote:
> On Sun, 2009-11-01 at 22:40 +0000, Matthew East wrote:
>> https://wiki.ubuntu.com/DocumentationTeam/ReleaseSchedule
>
> It looks good to me. I think it might be beneficial to add some
> deadlines for planning and proposals, though. This should help us to
> decide what needs to be done before it gets to three weeks before string
> freeze, as usual...

I agree that this would be desirable. Having said that I don't think
it should necessarily be a strictly enforced deadline, because I
wouldn't necessarily want to exclude a new contributor from coming in
later and driving forward a new document which can be made ready in
time for the "major new documentation" deadline, if there is time to
do so. But having a guideline date for planning would be good. I see
that the developers use week 5 - FeatureDefinitionFreeze - as their
deadline (in Lucid, 3 December 2009). Perhaps we could follow that,
although I'd be perfectly happy with setting aside more time for
planning.

It would also be good to merge some of the documents that you've
produced on planning into our style guide so that they can become
officially part of our process and linked to from relevant places.

-- 
Matthew East
http://www.mdke.org
gnupg pub 1024D/0E6B06FF