[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: doc branching
From: |
Cameron Horsburgh |
Subject: |
Re: doc branching |
Date: |
Sat, 08 Apr 2006 21:01:04 +1000 |
User-agent: |
Mail/News 1.5 (X11/20060228) |
Graham Percival wrote:
> 4. For the first half of the development cycle, don't include new
> features in the manual. New things get listed in NEWS, but only there.
> I favor this solution. At first glance, it might suggest that new
> features won't get documented well, but it should have the opposite
> effect: when I _do_ sit down to move new features from NEWS into the
> manual, I'll be doing them all at once, so I won't miss anything. I
> think we still have features introduced in 2.2 that haven't made it into
> the manual (I'll be calling for a volunteer to do this soon).
>
> Thoughts?
> - Graham
I'll have a bit of time over the next week--I'm willing to have a look
through the last few NEWS files (2.0 on?) and compare them with the
current (2.9 ?) manual. Any objections?
Cam
- Re: doc branching, (continued)
- Re: doc branching, Han-Wen Nienhuys, 2006/04/05
- Re: doc branching, Graham Percival, 2006/04/05
- Re: doc branching, Han-Wen Nienhuys, 2006/04/05
- Re: doc branching, Pedro Kröger, 2006/04/05
- Re: doc branching, Han-Wen Nienhuys, 2006/04/05
- Re: doc branching, Han-Wen Nienhuys, 2006/04/05
- Re: doc branching, Johannes Schindelin, 2006/04/05
- Re: doc branching, Graham Percival, 2006/04/05
- Re: doc branching, Han-Wen Nienhuys, 2006/04/05
- Re: doc branching, Graham Percival, 2006/04/05
Re: doc branching,
Cameron Horsburgh <=