> 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
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
