On 4/16/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
We seem to be getting in a habit of making changes to the 1.3 Branch and leaving them out of the trunk. Personally I think this is a bad idea for two reasons: 1) they may get forgotten - and we release a change in 1.3 thats then is effectively revereted when 1.4 comes out. 2) theres always the danger that someone comes along and makes larger changes that make porting more difficult I also think this is the wrong way round - we should be applying changes to the trunk and then back-porting them to the 1.3 branch (if required). For me the most up to date copy should if possible be the trunk and its better to apply and test changes there first.
I agree with this. Ongoing development leads the way, and if issues are found, they can be backported if necessary. IMHO, the root of the problem is that we branched S1 prematurely. If we don't think we're done with the 1.3 code line yet, then we shouldn't have branched it. Maybe I've not been paying enough attention, but I haven't seen much development going on in trunk yet, and without that, there's no good reason for two code lines. -- Martin Cooper Niall
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
