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