karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hendy Irawan <he...@soluvas.com>
Subject Re: Apache Karaf 2.3.0 very close
Date Sun, 14 Oct 2012 15:15:52 GMT
I highly support this alternative! :)

Using spring 3.1 for 2.3.1-SNAPSHOT and voting before the release would be
awesome! :)

Hendy

On Sun, Oct 14, 2012 at 6:59 PM, Christian Schneider [via Karaf] <
ml-node+s922171n4026390h61@n3.nabble.com> wrote:

> I think it depends on how compatible spring 3.1 is. So if we come to the
> conclusion that it should do no harm then we can deliver it of course.
> One way to test this would be a release candidate and give people some
> time to try it and give feedback. If we agree to go this way we should
> deliver the release candidate
> asap so people have maximum time to test. Then shortly before we do the
> 2.3.1 release we can vote if we should deliver spring 3.1 or spring 3.
>
> Christian
>
> Am 14.10.2012 13:23, schrieb Hendy Irawan:
>
> > I agree that 2.3.x should be bug fix releases. However Spring 3.1
> inclusion
> > isn't intended to fix a bug, merely because Spring 3.0  in Karaf 2.3.0
> was
> > an oversight, and that replacing it with Spring 3.1 will do little harm,
> if
> > any.
> >
> > Is 2.4 line actually necessary (how much farther can we push old Felix
> and
> > Servlet 2.5?), or it's just because of Spring...
> >
> > If so, then I think it's better to direct development to Karaf 3.0 full
> > throttle, while 2.3 is the last maintenance/stable line.
> >
> > Hendy
> >
> > On Sun, Oct 14, 2012 at 5:56 PM, Christian Schneider [via Karaf] <
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=4026390&i=0>>
> wrote:
> >
> >> While we could switch to spring 3.1 in karaf 2.4.0 I think we should
> not
> >> do it in 2.3.1.
> >>
> >> The reason is that 2.3.1 will be a bug fix release. So compatibility is
> >> the most important thing in these releases. The idea behind this is
> that
> >> people who need an important e.g. security fix should be able to update
> >> karaf without having to retest every deployment.
> >> As Spring 3.1 is a minor update not a bugfix update I think the switch
> >> should not go into a bugfix release of karaf.
> >>
> >> We do not really have an official policy like this at karaf but it is
> >> how I understand bugfix releases. So what do other think?
> >>
> >> Christian
> >>
> >> On 10/14/2012 12:38 PM, Hendy Irawan wrote:
> >>
> >>> I strongly support Spring 3.1 for future Karaf 2.3.1 :-)
> >>>
> >>> If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or
> >> can
> >>> use "spring30" feature. But I doubt anyone would ever need it
> >> (hopefully).
> >>> Hendy
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>
> http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html
> >>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
> >>
> >>
> >> ------------------------------
> >>   If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
>
> >> .
> >> NAML<
> http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> >>
> >
> >
>
>
> --
>
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026390.html
>  To unsubscribe from Apache Karaf 2.3.0 very close, click here<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4026295&code=aGVuZHlAc29sdXZhcy5jb218NDAyNjI5NXwxNTI0Njc4NzUy>
> .
> NAML<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
Hendy Irawan - on Twitter <http://twitter.com/hendybippo> - on
LinkedIn<http://id.linkedin.com/in/hendyirawan>
Web Developer | Bippo Indonesia <http://www.bippo.co.id/> | Akselerator
Bisnis | Bandung




--
View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026392.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.

Mime
View raw message