On Thu, Apr 10, 2008 at 4:43 AM, Mark Combellack <[EMAIL PROTECTED]> wrote: > > * Version 2.x will be the main focus > * Most of the development effort happens on Version 2.x > * We will make API changes which means that it will not be backwards > compatible with version 1 > * Version 1.x will go into "maintenance mode". > * May get some bug fixes and minor updates > > If my presumptions are correct then, from my point of view, we should keep > the trunk as the most up to date version - i.e. Version 2. > > Any maintenance for previous Version 1.x release should be done on their own > branches. >
+1 I still think this is the way we should go. As I said in my original proposal, I was expecting community members to have interest in keep maintaining and adding small enhancements to the 1.x branch, we have many users consuming releases from that branch, that might need bug fixes, etc. > > > ant also makes an interesting point about timing. Without clear goals and > objectives for Version 2.x, perhaps we should hold off on branching. > We have spent a good amount of time to make sure the 1.2 branch is very clean, and working perfectly for the release. With this said, I think it should be considered to be the source for 1.x branch, and we should consider cutting the branch at the moment we have 1.2 out of the door. > Mark > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
