Daft question, but is it not more sensible to have 3 branches here? head, old-head, and branch_2_1_fcs where:
branch_2_1_fcs is current stable use-this-one branch. For now it is what people should check out to get james source, but also keep it for any necessary maintenence releases later. head is new non-avalon version - "dont use this in a live server" type branch - will become release eventually head-old is current head. Obviously branch_2_1_fcs could be moved to head, and have a new branch for development of next gen? My argument is that head *should* evolve away from branch_2_1_fcs fairly quickly, but in the meantime people are still going to want the source for a stable uptodate james? Daniel. > -----Original Message----- > From: Danny Angus [mailto:[EMAIL PROTECTED] > Sent: 12 April 2005 09:39 > To: James Developers List > Subject: [PROPOSAL] > > > All, > > *THIS IS NOT A VOTE* Please would you review the following proposal, > *before* I ask for a vote on this too. > > I propose a Vote of Thanks to Noel J Bergman for the outstanding > service he has provided, and continues to provide the James project. > > I further propose that we believe it is unreasonable to expect Noel to > shoulder the burden of completing the merge of branch_2_1_fcs and > HEAD. > > I therefore further propose that branch_2_1_fcs be made HEAD and > evolved into James next version, and that HEAD be moved into an > archive branch from which specific items can be merged as and when > required. > > I suggest the following options: > > [ ] +1 I agree that branch_2_1_fcs as is should evolve into James next > major version > [ ] +0 I abstain > [ ] -1 I believe that HEAD and branch_2_1_fcs should merge, I am > prepared to undertake this work. > > --------------------------------------------------------------------- > 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]
