Documentation for the release

[David Miller]

Gervase Markham wrote:

> I could make time for such a hackathon this weekend, if others can get 
> their patches in before then and stay out of the way ;-). You can then 
> review the result in its entirety, by reading it, rather than as 
> patches. Does that sound do-able?

Quite frankly, that makes me a bit nervous.  I'm still remembering a 
major docs checkin about a year ago or so that went something along the 
lines of "hey guys, I just checked in a major revision to the 
documentation", which none of us knew was coming, and nobody had time to 
go back and audit.  At the time I just said "oh, I trust Gerv, we'll 
just hope it was good" and then over the following months, it turned out 
important things disappeared, and all of those changes that were also 
applicable to 2.16 never got backported to the 2.16 docs.

I'd very much prefer patches to each of the docs bugs for the specific 
things they cover (some of those bugs are for reorganization type 
changes, if I recall correctly, so some of them are ripe for 
larger-sized patches).

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Foundation       http://www.mozilla.org/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/