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 inst
On Sat, 10 Aug 2013 07:14:43 -0700 (PDT)
"Edward K. Ream" wrote:
> 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 ann
On Sat, Aug 10, 2013 at 9:31 AM, Terry Brown wrote:
> Releases also tend to follow a round of bug squashing, which I suppose
>
> is the same thing. I guess part of doing a release is clearing bugs
>
> from the tracker.
>
Yes. However, 4.11 a-1 will focus on installation and documentation
i
On Sat, 10 Aug 2013 07:14:43 -0700 (PDT)
"Edward K. Ream" wrote:
> 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 featur
