I don't know what is in subversion now. In order to continue we only need one thing as the absolute minimum: the current 2.1 (or 2.2? I assume these two are same) head in the subversion trunk directory. Everything else (current production release, current head) should be left at its current place. I guess this is the most productive process.
If later some other thing is needed, in subversion it is very easy (one
command) to rename, create, copy, move, create etc. a tag or branch or the
trunk. It is not necessary to decide about a new 2.2.1 release together with the replacement of head with the current 2.1 branch. The two questions are orthogonal, and combining them only makes the decision more complex.
----- Original Message ----- From: <[EMAIL PROTECTED]>
To: "'James Developers List'" <[email protected]>
Sent: Tuesday, April 12, 2005 11:19 AM
Subject: Re: [PROPOSAL]
The options and wording look good to me Danny. Also, unless anyone has any good reasons why not, that branch_2_1_fcs be made up as a final release.
-- Jason
I'm not a committer, but....
Wouldn't it be better to make a 2.2.1 release before starting with the big refactoring?
I think that most user will not upgrade to "next-version" soon and there are a few bugs fixed in the 2_1_fcs branch or posted in jira that should be applied and released.
Stefano
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
