Formalising a Release Schedule for Docs

[Phil Bull]

Hi Matt,

On Wed, 2009-11-04 at 13:24 +0000, Matthew East wrote:
> 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.

I agree that it should only be a soft deadline, and that FDF would be a
good time for it. I'd also like to propose that someone should post
reminders of deadlines to the mailing list a week or so before each
deadline. Otherwise, I'll end up forgetting...

> 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.

I'll work on that when I get some free time. Augustina's OpenWeek stuff
should probably find its way in there too.

Thanks,

Phil

-- 
Phil Bull
https://launchpad.net/people/philbull