You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2011/11/09 23:54:06 UTC
[PROPOSAL] Karaf 2.3.x branch
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Karaf 2.3.x could stop the JDK 1.5 compatibility.
Regards
JB
On 11/10/2011 12:16 AM, Jamie G. wrote:
> The concept of a 2.3.x branch to bridge the differences between 2.2.x
> and the to be 3.0.0 makes sense from the point of view of providing
> our user base an easier transition. I would like to know if we intend
> to keep JDK 1.5 compatibility on 2.3.x or if we'll have to enforce an
> update to JDK 1.6?
>
> Cheers,
> Jamie
>
> On Wed, Nov 9, 2011 at 7:24 PM, Jean-Baptiste Onofré<jb...@nanthrax.net> 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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Agree, I don't think it's required to maintain the JDK 1.5 on Karaf 2.3.x.
Regards
JB
On 11/10/2011 12:26 AM, Jamie G. wrote:
> It occurs more often that our desired dependencies require JDK 6.
> We've taken great care on the 2.1.x and 2.2.x lines to ensure JDK 5
> compatibility, if we drop this requirement on 2.3.x branch then it
> opens more opportunities to make things easier in transition to the
> Karaf 3.0 (JDK 6 minimum) code base.
>
> Cheers,
> Jamie
>
> On Wed, Nov 9, 2011 at 7:49 PM, Guillaume Nodet<gn...@gmail.com> wrote:
>> Not sure if forcing 1.6 is really required. Does that bring any value ?
>> Another way is does that even change anything for us ?
>>
>> On Wed, Nov 9, 2011 at 15:16, Jamie G.<ja...@gmail.com> wrote:
>>
>>> The concept of a 2.3.x branch to bridge the differences between 2.2.x
>>> and the to be 3.0.0 makes sense from the point of view of providing
>>> our user base an easier transition. I would like to know if we intend
>>> to keep JDK 1.5 compatibility on 2.3.x or if we'll have to enforce an
>>> update to JDK 1.6?
>>>
>>> Cheers,
>>> Jamie
>>>
>>> On Wed, Nov 9, 2011 at 7:24 PM, Jean-Baptiste Onofré<jb...@nanthrax.net>
>>> 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>
>>
>>
>> --
>> ------------------------
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Freeman Fang <fr...@gmail.com>.
+1 for 2.3.x Karaf branch and drop jdk 1.5 support.
Freeman
On 2011-11-10, at 上午7:28, Guillaume Nodet wrote:
> Makes sense, let's drop jdk 5 then.
>
> On Wed, Nov 9, 2011 at 15:26, Jamie G. <ja...@gmail.com>
> wrote:
>
>> It occurs more often that our desired dependencies require JDK 6.
>> We've taken great care on the 2.1.x and 2.2.x lines to ensure JDK 5
>> compatibility, if we drop this requirement on 2.3.x branch then it
>> opens more opportunities to make things easier in transition to the
>> Karaf 3.0 (JDK 6 minimum) code base.
>>
>> Cheers,
>> Jamie
>>
>> On Wed, Nov 9, 2011 at 7:49 PM, Guillaume Nodet <gn...@gmail.com>
>> wrote:
>>> Not sure if forcing 1.6 is really required. Does that bring any
>>> value ?
>>> Another way is does that even change anything for us ?
>>>
>>> On Wed, Nov 9, 2011 at 15:16, Jamie G. <ja...@gmail.com>
>>> wrote:
>>>
>>>> The concept of a 2.3.x branch to bridge the differences between
>>>> 2.2.x
>>>> and the to be 3.0.0 makes sense from the point of view of
>>>> providing
>>>> our user base an easier transition. I would like to know if we
>>>> intend
>>>> to keep JDK 1.5 compatibility on 2.3.x or if we'll have to
>>>> enforce an
>>>> update to JDK 1.6?
>>>>
>>>> Cheers,
>>>> Jamie
>>>>
>>>> On Wed, Nov 9, 2011 at 7:24 PM, Jean-Baptiste Onofré <jb@nanthrax.ne
>>>> t>
>>>> 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é
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> ------------------------
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> Open Source SOA
>>> http://fusesource.com
>>>
>>
>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
---------------------------------------------
Freeman Fang
FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Guillaume Nodet <gn...@gmail.com>.
Makes sense, let's drop jdk 5 then.
On Wed, Nov 9, 2011 at 15:26, Jamie G. <ja...@gmail.com> wrote:
> It occurs more often that our desired dependencies require JDK 6.
> We've taken great care on the 2.1.x and 2.2.x lines to ensure JDK 5
> compatibility, if we drop this requirement on 2.3.x branch then it
> opens more opportunities to make things easier in transition to the
> Karaf 3.0 (JDK 6 minimum) code base.
>
> Cheers,
> Jamie
>
> On Wed, Nov 9, 2011 at 7:49 PM, Guillaume Nodet <gn...@gmail.com> wrote:
> > Not sure if forcing 1.6 is really required. Does that bring any value ?
> > Another way is does that even change anything for us ?
> >
> > On Wed, Nov 9, 2011 at 15:16, Jamie G. <ja...@gmail.com> wrote:
> >
> >> The concept of a 2.3.x branch to bridge the differences between 2.2.x
> >> and the to be 3.0.0 makes sense from the point of view of providing
> >> our user base an easier transition. I would like to know if we intend
> >> to keep JDK 1.5 compatibility on 2.3.x or if we'll have to enforce an
> >> update to JDK 1.6?
> >>
> >> Cheers,
> >> Jamie
> >>
> >> On Wed, Nov 9, 2011 at 7:24 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> 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é
> >> > jbonofre@apache.org
> >> > http://blog.nanthrax.net
> >> > Talend - http://www.talend.com
> >> >
> >>
> >
> >
> >
> > --
> > ------------------------
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
> >
>
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by "Jamie G." <ja...@gmail.com>.
It occurs more often that our desired dependencies require JDK 6.
We've taken great care on the 2.1.x and 2.2.x lines to ensure JDK 5
compatibility, if we drop this requirement on 2.3.x branch then it
opens more opportunities to make things easier in transition to the
Karaf 3.0 (JDK 6 minimum) code base.
Cheers,
Jamie
On Wed, Nov 9, 2011 at 7:49 PM, Guillaume Nodet <gn...@gmail.com> wrote:
> Not sure if forcing 1.6 is really required. Does that bring any value ?
> Another way is does that even change anything for us ?
>
> On Wed, Nov 9, 2011 at 15:16, Jamie G. <ja...@gmail.com> wrote:
>
>> The concept of a 2.3.x branch to bridge the differences between 2.2.x
>> and the to be 3.0.0 makes sense from the point of view of providing
>> our user base an easier transition. I would like to know if we intend
>> to keep JDK 1.5 compatibility on 2.3.x or if we'll have to enforce an
>> update to JDK 1.6?
>>
>> Cheers,
>> Jamie
>>
>> On Wed, Nov 9, 2011 at 7:24 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>> 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é
>> > jbonofre@apache.org
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>> >
>>
>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Guillaume Nodet <gn...@gmail.com>.
Not sure if forcing 1.6 is really required. Does that bring any value ?
Another way is does that even change anything for us ?
On Wed, Nov 9, 2011 at 15:16, Jamie G. <ja...@gmail.com> wrote:
> The concept of a 2.3.x branch to bridge the differences between 2.2.x
> and the to be 3.0.0 makes sense from the point of view of providing
> our user base an easier transition. I would like to know if we intend
> to keep JDK 1.5 compatibility on 2.3.x or if we'll have to enforce an
> update to JDK 1.6?
>
> Cheers,
> Jamie
>
> On Wed, Nov 9, 2011 at 7:24 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> 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é
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by "Jamie G." <ja...@gmail.com>.
The concept of a 2.3.x branch to bridge the differences between 2.2.x
and the to be 3.0.0 makes sense from the point of view of providing
our user base an easier transition. I would like to know if we intend
to keep JDK 1.5 compatibility on 2.3.x or if we'll have to enforce an
update to JDK 1.6?
Cheers,
Jamie
On Wed, Nov 9, 2011 at 7:24 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Andreas Pieber <an...@gmail.com>.
Guillaume's approach sounds reasonable to me; making this clear should not
disturb development on master too much --> +1
On Thu, Nov 10, 2011 at 11:11, Guillaume Nodet <gn...@gmail.com> wrote:
> 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 <an...@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 <bcanhome@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é <jb...@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é
> > > >>> jbonofre@apache.org
> > > >>> http://blog.nanthrax.net
> > > >>> Talend - http://www.talend.com
> > > >>>
> > > >>
> > > >>
> > > > --
> > > > Jean-Baptiste Onofré
> > > > jbonofre@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
>
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <an...@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 <bcanhome@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é <jb...@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é
> > >>> jbonofre@apache.org
> > >>> http://blog.nanthrax.net
> > >>> Talend - http://www.talend.com
> > >>>
> > >>
> > >>
> > > --
> > > Jean-Baptiste Onofré
> > > jbonofre@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
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Andreas Pieber <an...@gmail.com>.
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 <bc...@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é <jb...@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é
> >>> jbonofre@apache.org
> >>> http://blog.nanthrax.net
> >>> Talend - http://www.talend.com
> >>>
> >>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbonofre@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/>
>
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Achim Nierbeck <bc...@googlemail.com>.
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é <jb...@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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@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/>
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Jean-Baptiste Onofré <jb...@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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by David Jencks <da...@yahoo.com>.
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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: [PROPOSAL] Karaf 2.3.x branch
Posted by Guillaume Nodet <gn...@gmail.com>.
I think as the number of compatibility breaking stuff grows in the 3.x
branch, the more welcomed a 2.3 release will be.
On Wed, Nov 9, 2011 at 14:54, Jean-Baptiste Onofré <jb...@nanthrax.net> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com