Graham Percival writes: > No argument there! Yes, more documentation about maintainability > the better.
I hope you're joking... The less documentation needed, whether it be for program usage, describing program bugs, build or release process, or maintainability, the better. No one likes to read documentation. What is really bad, is a situation where doing one of these things becomes some sort of puzzle, maze, time sink of trial and error, that could have been avoided by adding or sharing some minimal piece of documentation. However, documenting something that can also be automated is bad. Fixing a bug is much better than adding documentation about how to work around it. If you are tempted to document something, start with /why/ Greetings, Jan -- Jan Nieuwenhuizen <[email protected]> | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
