Re: The 0.18.0 release and Repository Rules

This and other ideas like it are definitely worth some thought. We 
should probably come up with a good process as group for :

1) When and how we should create and distribute patch files
2) Under what circumstances we should create branches in the repository 
for in progress features
3) Whether or not bug fix releases should be done on a branch and when 
that branch should be made

There are only three or four of us in the repository on a regular basis 
right now so we don't want to burden things with too much process. But 
we can at least start to think about how moto development should scale.

-Dave

On Wednesday, January 29, 2003, at 09:01  AM, Shay Harding wrote:

>> 	Its come to my attention that the repository hasn't
>> been in the best
>> of shape in the last few days. This is probably my fault :) . But
>> regardless, it seems that its about time to start putting
>> some process
>> around CVS commits. Starting now :
>>
>> 	1) Send me patches / diffs of all proposed changes and get my
>> approval. There are a number of cooks in this pot right now
>> and I need
>> to make sure I know what's going in :)
>
> Would it be possible to create a "patch" directory within the current
> repository for patch files? Would make it a lot easier to submit 
> patches
> and make sure nothing gets lost or overlooked. Commit the patch up, 
> then
> message/email you that there is one pending. Then all you'd have to do
> is run 'patch' against all the files and you're done.
>
> When you know you don't need a particular patch file any more it's a
> simple matter to cvs remove it.
>
>
>
> Shay
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.445 / Virus Database: 250 - Release Date: 1/21/2003
>
>
>