I think it would make sense to create this branch and release it after 3.0 so that we can have a good overview of what we can backport into that branch.
On Thu, Nov 10, 2011 at 00:34, Andreas Pieber <anpie...@gmail.com> wrote: > TBH I'm +/-0; It seams to me that we've discussed that topic already for 1 > million times or so :-) So, if we cant get out 3.0 fast we're left with no > other options than to go for 2.3; still I'm afraid this will lead to the > problem that ppl will rather implement features for 2.3 instead of 3.0 > because they expect a sooner 2.3 than 3.0 release... > > just my 2 cents, > > Kind regards, > Andreas > > On Thu, Nov 10, 2011 at 09:28, Achim Nierbeck <bcanh...@googlemail.com > >wrote: > > > Hi all, > > > > a big +1 from me for a 2.3 Branch, > > I can see the following additional improvements for the 2.3 branch while > > waiting for 3.0 line :) > > > > Upgrade to pax-web 1.1.x line since the 1.0.x line only does get > attention > > for critical bugfixes :) > > Also add the web shell comands to the 2.3 line would be highly > appreciated > > by our "customers" > > we already had a couple request to get those commands earlier in the 2.2 > > line ;) > > > > another +1 for dropping jdk 1.5 compatibly on the 2.3 line (due to jsf > > requirements with pax web we aren't even for the 2.2.x line if the web > > feature is used :) ) > > > > It will also give us a bit more time to get a thoroughly tested 3.0 > version > > out of the door. > > > > Regards, Achim > > > > 2011/11/10 Jean-Baptiste Onofré <j...@nanthrax.net> > > > > > Hi David, > > > > > > The fact is that we increased the scope between our first discussion > > about > > > Karaf 3.0 and the current roadmap. > > > > > > For instance, we decided to upgrade Karaf 3.0 to new version of Pax > Web, > > > change the shell commands, included some required cleanup and > > refactoring, > > > upgrade to a new OSGi release, upgrade to a new Aries version, etc. > > > > > > All these things mean major changes for the users. > > > > > > We all focus on the Karaf 3.0/trunk since at least a couple of months. > > For > > > instance, we spent time to fix the assemblies and distribution, etc. > > > > > > So we made, and we still make, very good progress on the Karaf 3.0 > > > release. Our team makes an awesome and really valuable work, most of us > > > during our spare time. > > > > > > However, regarding the issues we had (e.g. the Aries Blueprint 0.4 > > upgrade > > > wasn't smoothly at all) and the huge change, I think it makes sense to > > > address customers by creating a transition release. > > > > > > It doesn't mean that we gonna maintain 3 branches (trunk, 2.3.x, and > > > 2.2.x), it just means that we focus on trunk and merge some stuff on > > 2.3.x. > > > We let the 2.2.x branch as it is as it's very stable branch. > > > > > > My 0.02$ > > > > > > Regards > > > JB > > > > > > > > > On 11/10/2011 04:37 AM, David Jencks wrote: > > > > > >> IIRC during the summer we all agreed that 3.0 would be released for > > sure, > > >> certainly, without doubt, by the end of the summer, and everyone would > > >> enthusiastically help get it out. I don't think that really happened. > > >> > > >> I'd prefer that more effort go into releasing 3.0 with a finite set of > > >> changes rather than adding multiple kitchen sinks full of new features > > to > > >> 2.x. and never working on getting 3.0 done enough to release. If we > can > > >> get 3.0 out I have no problem with people (not including me) then > > >> backporting all the interesting features into 2.x. > > >> > > >> thanks > > >> david jencks > > >> > > >> On Nov 9, 2011, at 2:54 PM, Jean-Baptiste Onofré wrote: > > >> > > >> Hi all, > > >>> > > >>> we started to perform a bunch of changes on the Karaf trunk (future > > >>> Karaf 3.0 branch): refactoring on the commands to introduce the > > sub-shell, > > >>> update to Pax Web 2.0 and Jetty 8, renaming on the commands, new OSGi > > >>> release, new Aries version, etc. > > >>> > > >>> It means a huge change for the users. > > >>> > > >>> As our Karaf 2.2.x branch is our current stable branch, Guillaume > and I > > >>> discussed the creation of a Karaf 2.3.x branch (waiting the 3.0 > > release). > > >>> > > >>> This branch will include "minor" new features and dependencies > upgrade. > > >>> > > >>> Especially, I think it could be interesting to do on this branch: > > >>> - new OSGi release and framework update > > >>> - Aries update > > >>> - scp support and others minor new features > > >>> > > >>> WDYT ? > > >>> > > >>> Thanks > > >>> Regards > > >>> JB > > >>> -- > > >>> Jean-Baptiste Onofré > > >>> jbono...@apache.org > > >>> http://blog.nanthrax.net > > >>> Talend - http://www.talend.com > > >>> > > >> > > >> > > > -- > > > Jean-Baptiste Onofré > > > jbono...@apache.org > > > http://blog.nanthrax.net > > > Talend - http://www.talend.com > > > > > > > > > > > -- > > *Achim Nierbeck* > > > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer > & > > Project Lead > > blog <http://notizblog.nierbeck.de/> > > > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
