Michael Gratton wrote:
In the end, most of the pain caused by branches can usually be solved by having a well thought out commit policy and ensuring all comitters stick to that.
Actually there is at least one person on this list that is still learning about working with CVS in a distributed project. Whilst I do not have commit status, and do not expect to get it for a potentially long time I would like to know what is considered a "well thought out commit policy".
In return I will write up the suggested policy for the developer docs.
So can someone start me off...
Ross Gardler
