[quake3] Commit policy

Zachary Slater zakk at timedoctor.org
Wed Nov 29 16:10:31 EST 2006


Tim Angus wrote:
> Just to clarify some things:
> 
> * All development should take place on the trunk. This includes bug
> fixes, new features and experimental stuff.
> 
> * Release branches should not receive any commits that aren't also made
> to the trunk. Normally you /shouldn't/ commit to release branches as
> such commits are periodically merged from the trunk. These merges are
> harder to perform if there are sporadic commits made in the interim.
> 
> * Under NO CIRCUMSTANCES ever commit to a tag. A tag is a static
> snapshot which is intended to be unchanging.

Not only that, but due to this morning's fun I've just had to disable 
all ci access but for myself and Timbo, until we figure out how to 
revert back to 993 properly.




More information about the quake3 mailing list