Re: Trunk still not open

[Jambunathan K]

"Eric S. Raymond" <address@hidden> writes:

> +1 for a no-push without documentation policy.

Any policy should cater to the lowest commond denominator.  A lowest
common denominator would be

1. No release without documentation.
2. The original developer writes the documentation.

Trying to "synchornize" documentation and code is a stringent
requirement either in terms of the developer's preferred disposition or
the specific task at hand.

----------------------------------------------------------------

It is prudent to delay the documentation

1. When some code or feature churn is expected.  One the developer of
   the code intimately what compromises he has made for a particularl
   commit.

2. To put oneself in the right set of mood or context to surgically
   approach the task at hand.

   Speaking from my own experience, the info documentation comes out
   best when I have sufficiently distanced away from the feature in
   first place (to the point of even forgetting about it).

3. To make good of what one already has in the plate in terms of showing
   it to others, encouraging others to comment on it or to test the
   changes against real-life.

4. To "spread" the effort over a period of time.

One cannot overlook (4) particularly when volunteer effort is involved.