[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: doc branching
From: |
Werner LEMBERG |
Subject: |
Re: doc branching |
Date: |
Wed, 05 Apr 2006 09:45:44 +0200 (CEST) |
> 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).
5. Provide a unified documentation and mark features with a version
number, say,
This feature appeared in version 2.7.38.
Ideally, such things belong into the margin, but...
Werner
- doc branching, Graham Percival, 2006/04/05
- Re: doc branching,
Werner LEMBERG <=
- 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