commit policy (was: Re: SGML configuration patch)

[Joost van Baal]

On Tue, Jun 19, 2001 at 11:42:03AM -0400, Francis J. Lacoste wrote:
> I'm also more favorable to intensive bug fixing one week before fixing
> approach. 
<snip>
> 
> I would amend the commit policy to : "Make sure your changes run before
> commiting and documentation should be updated ASAP. Try not to break
> things for other platform though." :-)
> 
> While intense development continue, we should also try once in a while
> (once a week) the current tree on the supported platform to see what is
> broken.
> 
> Testing changes on all platform and waiting for documentation to be 
> up-to-date before commiting isn't very practical. This will slow down
> collaboration because changes will be delayed to the others.
> (We could be stricter on the documentation issue though if this becomes
>  a problem: documentation always lagging to much behind.)

Sounds reasonable, like Egon's message.  I updated the developers
manual, to reflect this.

Bye,

Joost


-- 
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of 
"unsubscribe". Trouble? Send an email with subject "help" to 
development-request at logreport.org