On Tue, Aug 16, 2011 at 12:39 PM, Duncan <[email protected]> wrote: > But then the docs folks said the policy was only to document stable, and > that they weren't going to document openrc until it was going stable.
Well, I can see their point - OpenRC was the future for probably 2 years before it actually happened. Certainly it wouldn't make sense to keep all the official docs updated for that entire period of time. I think this boils down to basic release management - decide to do something in a certain timeframe, open blockers, announce the last call, and then just make it happen (no new blockers allowed without approval by the project lead or the council). Once you can see the light at the end of the tunnel the doc request goes in and becomes a blocker. I think that this mostly happens already. We just need to make sure the docs stay as a blocker. In the case of OpenRC I'd treat the baselayout 1/2 versions of the documentation as separate branches and then make the switch all at once. That said, I don't run the docs team, the openrc team, or the /usr-is-required team, so feel free to chime in with whatever I missed... Rich
