You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Gert Vanthienen <ge...@skynet.be> on 2009/02/12 19:07:04 UTC
[DISCUSS] Release frequency for components
L.S.,
A while back, we separated the components into a separate build so they
could be shared between ServiceMix 3 and ServiceMix 4, but we also made
every component a Maven project on its own to allow them to be released
independently. Up to now, we didn't really leverage all the hard work
that was done to make this happen, but we might have a good opportunity
to start the habit now:
- Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0
component in Servicemix, so we could do with a release of servicemix-camel
- I guess the same also goes for CXF, we should be able to release a new
CXF component whenever CXF itself is released
On the other hand, I think we are also waiting for a Spring DM 1.2.0
release to get a full set of components released again, so it might be
better to just wait a little while and do a full component release once
more before we start our new best habit.
Once again: thought? suggestions?
Regards,
Gert
Re: [DISCUSS] Release frequency for components
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
On Thursday 12 February 2009 - 19:07, Gert Vanthienen wrote:
> L.S.,
>
> A while back, we separated the components into a separate build so they
> could be shared between ServiceMix 3 and ServiceMix 4, but we also made
> every component a Maven project on its own to allow them to be released
> independently. Up to now, we didn't really leverage all the hard work
> that was done to make this happen, but we might have a good opportunity
> to start the habit now:
> - Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0
> component in Servicemix, so we could do with a release of
> servicemix-camel
> - I guess the same also goes for CXF, we should be able to release a new
> CXF component whenever CXF itself is released
>
> On the other hand, I think we are also waiting for a Spring DM 1.2.0
> release to get a full set of components released again, so it might be
> better to just wait a little while and do a full component release once
> more before we start our new best habit.
>
> Once again: thought? suggestions?
>
> Regards,
>
> Gert
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086
Re: [DISCUSS] Release frequency for components
Posted by Freeman Fang <fr...@gmail.com>.
+1
Freeman
Gert Vanthienen wrote:
> L.S.,
>
> A while back, we separated the components into a separate build so
> they could be shared between ServiceMix 3 and ServiceMix 4, but we
> also made every component a Maven project on its own to allow them to
> be released independently. Up to now, we didn't really leverage all
> the hard work that was done to make this happen, but we might have a
> good opportunity to start the habit now:
> - Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0
> component in Servicemix, so we could do with a release of
> servicemix-camel
> - I guess the same also goes for CXF, we should be able to release a
> new CXF component whenever CXF itself is released
>
> On the other hand, I think we are also waiting for a Spring DM 1.2.0
> release to get a full set of components released again, so it might be
> better to just wait a little while and do a full component release
> once more before we start our new best habit.
>
> Once again: thought? suggestions?
>
> Regards,
>
> Gert
>
Re: [DISCUSS] Release frequency for components
Posted by Chris Custine <ch...@gmail.com>.
+1
I think we should do an update release of all components around the same
time we do the 4.0 release, and then do individual releases after that. I
think it is going to be important to document and track the components
slightly differently than we do now so that releases are as easy as
possible. I think you are covering that in a different thread so I will
respond to that as well.
Chris
--
Chris Custine
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Directory Server :: http://directory.apache.org
On Thu, Feb 12, 2009 at 11:07 AM, Gert Vanthienen <gert.vanthienen@skynet.be
> wrote:
> L.S.,
>
> A while back, we separated the components into a separate build so they
> could be shared between ServiceMix 3 and ServiceMix 4, but we also made
> every component a Maven project on its own to allow them to be released
> independently. Up to now, we didn't really leverage all the hard work that
> was done to make this happen, but we might have a good opportunity to start
> the habit now:
> - Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0 component
> in Servicemix, so we could do with a release of servicemix-camel
> - I guess the same also goes for CXF, we should be able to release a new
> CXF component whenever CXF itself is released
>
> On the other hand, I think we are also waiting for a Spring DM 1.2.0
> release to get a full set of components released again, so it might be
> better to just wait a little while and do a full component release once more
> before we start our new best habit.
>
> Once again: thought? suggestions?
>
> Regards,
>
> Gert
>
Re: [DISCUSS] Release frequency for components
Posted by Ulhas Bhole <ul...@progress.com>.
+1, Agree with Chris and Edell on waiting till 4.0 release.
-- Ulhas
Edell Nolan wrote:
> +1 - I would wait for 4.0 as Chris mentioned as we will have all the
> components released together and will be easier to track from that and they
> will all be releeased with Spring DM 1.2.0
>
> On Fri, Feb 13, 2009 at 1:42 PM, jgoodyear <ja...@gmail.com> wrote:
>
>
>> +1
>>
>>
>> Gert Vanthienen wrote:
>>
>>> L.S.,
>>>
>>> A while back, we separated the components into a separate build so they
>>> could be shared between ServiceMix 3 and ServiceMix 4, but we also made
>>> every component a Maven project on its own to allow them to be released
>>> independently. Up to now, we didn't really leverage all the hard work
>>> that was done to make this happen, but we might have a good opportunity
>>> to start the habit now:
>>> - Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0
>>> component in Servicemix, so we could do with a release of
>>>
>> servicemix-camel
>>
>>> - I guess the same also goes for CXF, we should be able to release a new
>>> CXF component whenever CXF itself is released
>>>
>>> On the other hand, I think we are also waiting for a Spring DM 1.2.0
>>> release to get a full set of components released again, so it might be
>>> better to just wait a little while and do a full component release once
>>> more before we start our new best habit.
>>>
>>> Once again: thought? suggestions?
>>>
>>> Regards,
>>>
>>> Gert
>>>
>>>
>>> -----
>>> ---
>>> Gert Vanthienen
>>> http://gertvanthienen.blogspot.com
>>>
>>>
>> -----
>> Jamie Goodyear
>> ------------------------
>> Blog: http://icodebythesea.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>> --
>> View this message in context:
>> http://www.nabble.com/-DISCUSS--Release-frequency-for-components-tp21981581p21996547.html
>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>>
>>
>>
>
>
Re: [DISCUSS] Release frequency for components
Posted by Edell Nolan <ed...@gmail.com>.
+1 - I would wait for 4.0 as Chris mentioned as we will have all the
components released together and will be easier to track from that and they
will all be releeased with Spring DM 1.2.0
On Fri, Feb 13, 2009 at 1:42 PM, jgoodyear <ja...@gmail.com> wrote:
>
> +1
>
>
> Gert Vanthienen wrote:
> >
> > L.S.,
> >
> > A while back, we separated the components into a separate build so they
> > could be shared between ServiceMix 3 and ServiceMix 4, but we also made
> > every component a Maven project on its own to allow them to be released
> > independently. Up to now, we didn't really leverage all the hard work
> > that was done to make this happen, but we might have a good opportunity
> > to start the habit now:
> > - Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0
> > component in Servicemix, so we could do with a release of
> servicemix-camel
> > - I guess the same also goes for CXF, we should be able to release a new
> > CXF component whenever CXF itself is released
> >
> > On the other hand, I think we are also waiting for a Spring DM 1.2.0
> > release to get a full set of components released again, so it might be
> > better to just wait a little while and do a full component release once
> > more before we start our new best habit.
> >
> > Once again: thought? suggestions?
> >
> > Regards,
> >
> > Gert
> >
> >
> > -----
> > ---
> > Gert Vanthienen
> > http://gertvanthienen.blogspot.com
> >
>
>
> -----
> Jamie Goodyear
> ------------------------
> Blog: http://icodebythesea.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
> --
> View this message in context:
> http://www.nabble.com/-DISCUSS--Release-frequency-for-components-tp21981581p21996547.html
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>
>
Re: [DISCUSS] Release frequency for components
Posted by jgoodyear <ja...@gmail.com>.
+1
Gert Vanthienen wrote:
>
> L.S.,
>
> A while back, we separated the components into a separate build so they
> could be shared between ServiceMix 3 and ServiceMix 4, but we also made
> every component a Maven project on its own to allow them to be released
> independently. Up to now, we didn't really leverage all the hard work
> that was done to make this happen, but we might have a good opportunity
> to start the habit now:
> - Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0
> component in Servicemix, so we could do with a release of servicemix-camel
> - I guess the same also goes for CXF, we should be able to release a new
> CXF component whenever CXF itself is released
>
> On the other hand, I think we are also waiting for a Spring DM 1.2.0
> release to get a full set of components released again, so it might be
> better to just wait a little while and do a full component release once
> more before we start our new best habit.
>
> Once again: thought? suggestions?
>
> Regards,
>
> Gert
>
>
> -----
> ---
> Gert Vanthienen
> http://gertvanthienen.blogspot.com
>
-----
Jamie Goodyear
------------------------
Blog: http://icodebythesea.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
--
View this message in context: http://www.nabble.com/-DISCUSS--Release-frequency-for-components-tp21981581p21996547.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: [DISCUSS] Release frequency for components
Posted by Lars Heinemann <lh...@apache.org>.
Fully agreed.
+1
Lars
Gert Vanthienen schrieb:
> L.S.,
>
> A while back, we separated the components into a separate build so
> they could be shared between ServiceMix 3 and ServiceMix 4, but we
> also made every component a Maven project on its own to allow them to
> be released independently. Up to now, we didn't really leverage all
> the hard work that was done to make this happen, but we might have a
> good opportunity to start the habit now:
> - Camel 1.6.0 is being voted and we don't even have a Camel 1.5.0
> component in Servicemix, so we could do with a release of
> servicemix-camel
> - I guess the same also goes for CXF, we should be able to release a
> new CXF component whenever CXF itself is released
>
> On the other hand, I think we are also waiting for a Spring DM 1.2.0
> release to get a full set of components released again, so it might be
> better to just wait a little while and do a full component release
> once more before we start our new best habit.
>
> Once again: thought? suggestions?
>
> Regards,
>
> Gert