On 9/13/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:

True, but I think the trunk should always represent the next release of
Roller.  So once 3.0 goes public then the trunk should represent 3.1 in
development.  Once we think 3.1 is done we copy trunk ->
branches/roller_3.1 and go through the RC process.

I agree that the trunk should always represent current development.
For folks that aren't involved in releasing and bug fixes, it's nice
to know we should just checkout the trunk if we want to contribute/fix
code.

Matt

Reply via email to