In Getting Things Done, David Allen recommends that we stop and ask we are doing our projects. Here are two answers.
I do formal releases for two, no three reasons: 1. To force myself to document features. 2. To announce that the particular code base is to be trusted. 3. To test and correct installers and installation instructions and install scripts. Point 2 is somewhat dubious, imo, but some people and organizations find it comforting ;-) Documentation has several purposes: 1. Most importantly, to announce that a particular feature exists. People have no way of trying feature otherwise. 2. To provide the *minimum* need for people to start using a feature. 3. Least importantly, to provide all the details. It's easy to overlook these priorities. Often, we seem to get them backwards by jumping in with the details before explaining what a feature does! I'll attempt to keep them in mind as I revise the release notes. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
