I kinda agree with David here. IIRC, we decided to go for a 3.0 mainly because of the switch to JDK 1.6. So we should release that asap and add more features when they are ready in the following 3.1 and 3.2 releases. I'm not really in favor of maintaining two development versions (2.3 and 3.0) at the same time.
However, having a 3.0 will certainly break most of the existing downstream projects, as they certainly use a [2.2,3.0) range for imports, meaning they won't deploy on the new 3.0, so we definitely not to do that unless we need. So my position would be continue on 2.x and drop jdk 1.6 compatibility in 2.3. I think other projects have done that too and I haven't heard many complaints. On Sat, Apr 16, 2011 at 00:39, Jamie G. <[email protected]> wrote: > It's a bit of a balancing act here deciding against a new 2.x branch > and a proper 3.0 release I agree. The general concern I think is > providing enough time for large number of major changes to appear in > version 3 trunk. Where major changes denote a large departure from how > Karaf 2.x works. By making a 2.3 branch we give some breathing space > for 3.0 development to continue. That being said if the community is > more in favor of pushing up the 3.0 date instead of a 2.3 branch then > that could work as well. > > Jamie > > On Fri, Apr 15, 2011 at 7:41 PM, David Jencks <[email protected]> wrote: >> I think an alternative would be to release 3.0.0 soon and put the new >> features on trunk. I've found that its much easier to create new branches >> than to maintain them. Could someone explain why a new branch is better >> than a soon 3.0.0 release? >> >> thanks >> david jencks >> >> >> On Apr 15, 2011, at 8:50 AM, Jamie G. wrote: >> >>> Hi All, >>> >>> There has been a number of discussions regarding trying out new >>> features on the 2.x branch while we are continuing to work towards a >>> 3.0.x release, as such I think it may be worth discussing if we'd like >>> to create a Karaf 2.3 branch? >>> >>> This branch would contain new features to the 2.x branch, and back >>> ported features from the 3.0 line. As this is a 2.x branch it would >>> continue to be JDK 1.5 & m2 compatible - we move to JKD 1.6 & m3 on >>> the Karaf 3.0 line. >>> >>> At this point I would presume the logical branch cut line would be >>> starting from the 2.2.1 tag once available? The 2.2.x line would >>> continue on in support mode, with 2.3.x collecting new features. >>> >>> Cheers, >>> Jamie >> >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com Connect at CamelOne May 24-26 The Open Source Integration Conference http://camelone.com/
