You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Hadrian Zbarcea <hz...@gmail.com> on 2011/06/09 14:47:33 UTC
[DISCUSS] Closing down for the 2.8.0 release
Hi,
I would propose starting to close down and prepare for the 2.8.0 release
in 2-3 weeks. There are already 282 issues for 2.8.0 and chances are
will be over 300 by the release time, probably setting a new record.
As of now there are 17 issues unresolved, a few of them almost done, so
by next week I assume there'll be significantly less. I would suggest
shifting the focus from adding new features to stabilizing the build. If
there are any issues you know of that you think absolutely must be in
2.8.0 please shout and ask for help if needed (especially non committers
subscribing to this list).
Thoughts?
Hadrian
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday, July 06, 2011 10:09:14 AM Willem Jiang wrote:
> Hi Hadrian,
>
> I think we are ready for the Camel 2.8.0 release.
> But I'm not sure why you are still planing to do the patch release for
> the 2.7.x as we never do this kind small patch release unless it relates
> to a serious security issue before.
>
If I get a chance tomorrow, I'll probably go through some of the other pure
bug fixes and pull them back in as well. I started looking through some of
them, just got busy on some other work related things.
> Can we just let the people move on to Camel 2.8.0 instead of confusing
> about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
I don't think it's been confusing for CXF users and finding ways to get bug
fixes to users without requiring big updates is a good thing. I definitely
support maintaining fixes branches for a while.
Dan
>
> On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
> > Karaf 2.2.2 is now available and Willem did the upgrade. I think we can
> > get ready to start the release. Are there any other issues that must go
> > into 2.8.0?
> >
> > I would also build a 2.7.3 at the same time, there are a few fixes and
> > improvements, including some around xmlsecurity.
> >
> > Thoughts?
> > Hadrian
> >
> > On 06/30/2011 11:07 PM, Willem Jiang wrote:
> >> Hi,
> >>
> >> I just applied the patch into trunk.
> >>
> >> On 7/1/11 12:36 AM, Donald Whytock wrote:
> >>> https://issues.apache.org/jira/browse/CAMEL-3948
> >>>
> >>> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com>
> >>>
> >>> wrote:
> >>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current
> >>>> trunk
> >>>> still needs my final patch.
> >>>>
> >>>> Don
> >>>>
> >>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
> >>>>
> >>>> Onofré<jb...@nanthrax.net> wrote:
> >>>>> Hi Claus,
> >>>>>
> >>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies
> >>>>> yesterday.
> >>>>> Jamie
> >>>>> will cut off the release this afternoon.
> >>>>>
> >>>>> Regards
> >>>>> JB
> >>>>>
> >>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
> >>>>>> Hi
> >>>>>>
> >>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2
> >>>>>> open
> >>>>>> tickets.
> >>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
> >>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
> >>>>>>
> >>>>>> CAMEL-3774 is about generating the manual and is assigned to
> >>>>>> Hadrian.
> >>>>>>
> >>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is
> >>>>>> in
> >>>>>> progress.
> >>>>>> So by good chance we should be able to pickup that version
> >>>>>> when its
> >>>>>> released.
> >>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
> >>>>>> (CAMEL-4144 is about some maven validate goal that would
> >>>>>> require
> >>>>>> Karaf
> >>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
> >>>>>> absolutely fine)
> >>>>>>
> >>>>>> The CI servers also seems good. Although they tend to run out
> >>>>>> of
> >>>>>> memory at the end, such as when testing the examples. But
> >>>>>> those are
> >>>>>> the last piece of the build, and thus all components tests
> >>>>>> fine.
> >>>>>>
> >>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins
> >>>>>> on
> >>>>>> the CI
> >>>>>> servers and then start cutting the Camel 2.8 release. Would be
> >>>>>> good to
> >>>>>> get it out before the summer vacation starts. As well its more
> >>>>>> than 3 months since Camel 2.7 was released.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus
> >>>>>> Ibsen<cl...@gmail.com>
> >>>>>>
> >>>>>> wrote:
> >>>>>>> Hi
> >>>>>>>
> >>>>>>> Okay we should really start focusing on getting the last
> >>>>>>> tickets
> >>>>>>> which
> >>>>>>> has been assigned for 2.8 release done now.
> >>>>>>> There is about 350 tickets on the roadmap, so its going to
> >>>>>>> be the
> >>>>>>> biggest release, since 2.0 went GA.
> >>>>>>>
> >>>>>>> So please take a look at your assigned tickets and get them
> >>>>>>> done, or move them for 2.9.
> >>>>>>> Then keep eyes on CI servers and help fix any test failures,
> >>>>>>> so we
> >>>>>>> have green builds.
> >>>>>>>
> >>>>>>> The summer vacation period is approaching so we should IMHO
> >>>>>>> get the
> >>>>>>> 2.8 release out early next month if possible.
> >>>>>>>
> >>>>>>>
> >>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian
> >>>>>>> Zbarcea<hz...@gmail.com>
> >>>>>>>
> >>>>>>> wrote:
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> I would propose starting to close down and prepare for the
> >>>>>>>> 2.8.0
> >>>>>>>> release
> >>>>>>>> in
> >>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and
> >>>>>>>> chances are
> >>>>>>>> will
> >>>>>>>> be
> >>>>>>>> over 300 by the release time, probably setting a new
> >>>>>>>> record.
> >>>>>>>>
> >>>>>>>> As of now there are 17 issues unresolved, a few of them
> >>>>>>>> almost
> >>>>>>>> done, so
> >>>>>>>> by
> >>>>>>>> next week I assume there'll be significantly less. I would
> >>>>>>>> suggest
> >>>>>>>> shifting
> >>>>>>>> the focus from adding new features to stabilizing the
> >>>>>>>> build. If
> >>>>>>>> there
> >>>>>>>> are
> >>>>>>>> any issues you know of that you think absolutely must be
> >>>>>>>> in 2.8.0
> >>>>>>>> please
> >>>>>>>> shout and ask for help if needed (especially non
> >>>>>>>> committers
> >>>>>>>> subscribing
> >>>>>>>> to
> >>>>>>>> this list).
> >>>>>>>>
> >>>>>>>> Thoughts?
> >>>>>>>>
> >>>>>>>> Hadrian
> >>>>>>>
> >>>>>>> --
> >>>>>>> Claus Ibsen
> >>>>>>> -----------------
> >>>>>>> FuseSource
> >>>>>>> Email: cibsen@fusesource.com
> >>>>>>> Web: http://fusesource.com
> >>>>>>> Twitter: davsclaus, fusenews
> >>>>>>> Blog: http://davsclaus.blogspot.com/
> >>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Jul 6, 2011 at 10:57 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Just spotted test errors in camel-smpp.
>
I have commited a fix for those tests. It was a missing easymock
expectation that needed to be added due a new feature added to the
camel-smpp component in ticket CAMEL-4170.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
Just spotted test errors in camel-smpp.
I guess its because some commits in that component recently caused these errors.
It fails flat out on my laptop this morning as well.
Failed tests:
processShouldCreateTheSmppSession(org.apache.camel.component.smpp.SmppProducerLazySessionCreationTest)
processInOnlyShouldSendASubmitSmAndUpdateTheExchangeInMessage(org.apache.camel.component.smpp.SmppProducerTest)
processInOutShouldSendASubmitSmAndUpdateTheExchangeOutMessage(org.apache.camel.component.smpp.SmppProducerTest)
processInOutShouldHonorTheDataCoding(org.apache.camel.component.smpp.SmppProducerTest)
Also reported by Apache CI
https://builds.apache.org/job/Camel.trunk.fulltest/org.apache.camel$camel-smpp/355/testReport/
On Wed, Jul 6, 2011 at 10:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
> On Tue, Jul 5, 2011 at 6:11 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
>> Karaf 2.2.2 is now available and Willem did the upgrade. I think we can get
>> ready to start the release. Are there any other issues that must go into
>> 2.8.0?
>
> I checked the commit log and spotted some minor issues which I have corrected.
> We should kick the CI server to ensure the code dont have test
> failures, before we start cutting a release.
>
> Please refrain from adding more features and focus on bug and test
> fixes. So the code is stable and a release can be cut the sooner the
> better.
>
>
>
>>
>> I would also build a 2.7.3 at the same time, there are a few fixes and
>> improvements, including some around xmlsecurity.
>>
>> Thoughts?
>> Hadrian
>>
>>
>> On 06/30/2011 11:07 PM, Willem Jiang wrote:
>>>
>>> Hi,
>>>
>>> I just applied the patch into trunk.
>>>
>>> On 7/1/11 12:36 AM, Donald Whytock wrote:
>>>>
>>>> https://issues.apache.org/jira/browse/CAMEL-3948
>>>>
>>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com>
>>>> wrote:
>>>>>
>>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current trunk
>>>>> still needs my final patch.
>>>>>
>>>>> Don
>>>>>
>>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>>>> Onofré<jb...@nanthrax.net> wrote:
>>>>>>
>>>>>> Hi Claus,
>>>>>>
>>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday.
>>>>>> Jamie
>>>>>> will cut off the release this afternoon.
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>>>>>> tickets.
>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>>>
>>>>>>> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>>>>>>>
>>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in
>>>>>>> progress.
>>>>>>> So by good chance we should be able to pickup that version when its
>>>>>>> released.
>>>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>>>>> (CAMEL-4144 is about some maven validate goal that would require Karaf
>>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>>>>>> absolutely fine)
>>>>>>>
>>>>>>> The CI servers also seems good. Although they tend to run out of
>>>>>>> memory at the end, such as when testing the examples. But those are
>>>>>>> the last piece of the build, and thus all components tests fine.
>>>>>>>
>>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
>>>>>>> servers and then start cutting the Camel 2.8 release. Would be good to
>>>>>>> get it out before the summer vacation starts. As well its more than 3
>>>>>>> months since Camel 2.7 was released.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Okay we should really start focusing on getting the last tickets
>>>>>>>> which
>>>>>>>> has been assigned for 2.8 release done now.
>>>>>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>>>>>> biggest release, since 2.0 went GA.
>>>>>>>>
>>>>>>>> So please take a look at your assigned tickets and get them done, or
>>>>>>>> move them for 2.9.
>>>>>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>>>>>> have green builds.
>>>>>>>>
>>>>>>>> The summer vacation period is approaching so we should IMHO get the
>>>>>>>> 2.8 release out early next month if possible.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I would propose starting to close down and prepare for the 2.8.0
>>>>>>>>> release
>>>>>>>>> in
>>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are
>>>>>>>>> will
>>>>>>>>> be
>>>>>>>>> over 300 by the release time, probably setting a new record.
>>>>>>>>>
>>>>>>>>> As of now there are 17 issues unresolved, a few of them almost
>>>>>>>>> done, so
>>>>>>>>> by
>>>>>>>>> next week I assume there'll be significantly less. I would suggest
>>>>>>>>> shifting
>>>>>>>>> the focus from adding new features to stabilizing the build. If
>>>>>>>>> there
>>>>>>>>> are
>>>>>>>>> any issues you know of that you think absolutely must be in 2.8.0
>>>>>>>>> please
>>>>>>>>> shout and ask for help if needed (especially non committers
>>>>>>>>> subscribing
>>>>>>>>> to
>>>>>>>>> this list).
>>>>>>>>>
>>>>>>>>> Thoughts?
>>>>>>>>>
>>>>>>>>> Hadrian
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> FuseSource
>>>>>>>> Email: cibsen@fusesource.com
>>>>>>>> Web: http://fusesource.com
>>>>>>>> Twitter: davsclaus, fusenews
>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Tue, Jul 5, 2011 at 6:11 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> Karaf 2.2.2 is now available and Willem did the upgrade. I think we can get
> ready to start the release. Are there any other issues that must go into
> 2.8.0?
I checked the commit log and spotted some minor issues which I have corrected.
We should kick the CI server to ensure the code dont have test
failures, before we start cutting a release.
Please refrain from adding more features and focus on bug and test
fixes. So the code is stable and a release can be cut the sooner the
better.
>
> I would also build a 2.7.3 at the same time, there are a few fixes and
> improvements, including some around xmlsecurity.
>
> Thoughts?
> Hadrian
>
>
> On 06/30/2011 11:07 PM, Willem Jiang wrote:
>>
>> Hi,
>>
>> I just applied the patch into trunk.
>>
>> On 7/1/11 12:36 AM, Donald Whytock wrote:
>>>
>>> https://issues.apache.org/jira/browse/CAMEL-3948
>>>
>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com>
>>> wrote:
>>>>
>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current trunk
>>>> still needs my final patch.
>>>>
>>>> Don
>>>>
>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>>> Onofré<jb...@nanthrax.net> wrote:
>>>>>
>>>>> Hi Claus,
>>>>>
>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday.
>>>>> Jamie
>>>>> will cut off the release this afternoon.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>>>>> tickets.
>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>>
>>>>>> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>>>>>>
>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in
>>>>>> progress.
>>>>>> So by good chance we should be able to pickup that version when its
>>>>>> released.
>>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>>>> (CAMEL-4144 is about some maven validate goal that would require Karaf
>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>>>>> absolutely fine)
>>>>>>
>>>>>> The CI servers also seems good. Although they tend to run out of
>>>>>> memory at the end, such as when testing the examples. But those are
>>>>>> the last piece of the build, and thus all components tests fine.
>>>>>>
>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
>>>>>> servers and then start cutting the Camel 2.8 release. Would be good to
>>>>>> get it out before the summer vacation starts. As well its more than 3
>>>>>> months since Camel 2.7 was released.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Okay we should really start focusing on getting the last tickets
>>>>>>> which
>>>>>>> has been assigned for 2.8 release done now.
>>>>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>>>>> biggest release, since 2.0 went GA.
>>>>>>>
>>>>>>> So please take a look at your assigned tickets and get them done, or
>>>>>>> move them for 2.9.
>>>>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>>>>> have green builds.
>>>>>>>
>>>>>>> The summer vacation period is approaching so we should IMHO get the
>>>>>>> 2.8 release out early next month if possible.
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I would propose starting to close down and prepare for the 2.8.0
>>>>>>>> release
>>>>>>>> in
>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are
>>>>>>>> will
>>>>>>>> be
>>>>>>>> over 300 by the release time, probably setting a new record.
>>>>>>>>
>>>>>>>> As of now there are 17 issues unresolved, a few of them almost
>>>>>>>> done, so
>>>>>>>> by
>>>>>>>> next week I assume there'll be significantly less. I would suggest
>>>>>>>> shifting
>>>>>>>> the focus from adding new features to stabilizing the build. If
>>>>>>>> there
>>>>>>>> are
>>>>>>>> any issues you know of that you think absolutely must be in 2.8.0
>>>>>>>> please
>>>>>>>> shout and ask for help if needed (especially non committers
>>>>>>>> subscribing
>>>>>>>> to
>>>>>>>> this list).
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>> Hadrian
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> FuseSource
>>>>>>> Email: cibsen@fusesource.com
>>>>>>> Web: http://fusesource.com
>>>>>>> Twitter: davsclaus, fusenews
>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Willem Jiang <wi...@gmail.com>.
Just be clear, we spend lots of time on Camel trunk which can benefit
for all the Camel user (includes Talend customer).
Porting the fixes is just a small part of the work. I don't want the
patch work slow down our daily contribution to the trunk.
On 7/7/11 10:48 AM, Daniel Kulp wrote:
> On Thursday, July 07, 2011 10:40:50 AM Willem Jiang wrote:
>> OK, I see the patch rule is based on the Talend customer.
>
> To be clear, I didn't say this is driven by a Talend customer. Again, they
> don't care if it's done here or in a private repo or something. However, if
> I'm doing some work for a Talend customer, it makes sense to me that everyone
> can benefit from it. This can be perfectly applied for Fuse as well. I
> know you spend a lot of time porting fixes back to 2.7.x (and 2.6.x, etc...)
> for Fuse customers. Other Camel users COULD benefit from that work as well.
> That's completely up to you guys though.
>
> Dan
>
>
>>
>> On 7/6/11 9:32 PM, Daniel Kulp wrote:
>>> One other note:
>>>
>>> Talend has customers on 2.7.x that are not likely to move to 2.8.0 any
>>> time soon. As Christian pointed out, lots of companies use a 6-8
>>> month cycle, Some longer, some shorter, and won't move off what they
>>> have for quite a bit of time. Thus, no matter what, I am going to
>>> have to port some bug fixes back to 2.7.x. There isn't anyway for me
>>> to avoid that (unless I tell my customers "too bad, no fixes" which
>>> would not go over well :-) ). I COULD do the porting on some private
>>> fork of the Camel branches and deliver the fixes to the customers that
>>> way. That's definitely a perfectly valid way to do it. In that case,
>>> all my work really would just benefit a small number of Camel users.
>>> I'd MUCH MUCH prefer to do the porting here and allow my work to
>>> benefit the entire Camel community. It's the exact same amount of
>>> work, just in a different place. (well, I suppose if the fork is using
>>> git, it could be a little less work as merging with git is so much
>>> nicer and faster, but still, that's minor)
>>>
>>> Likewise for releases. I could create private releases and stick them
>>> in a "talend" repository someplace (and in some cases, I may need to do
>>> that anyway), but I could also do roughly the same amount of work here
>>> (calling the vote is additional work here, but that's minor) and the
>>> entire Camel user base benefits. In addition, the releases here would
>>> go to central which makes our customers happy. (no Nexus updates,
>>> firewall rules updates, etc...)
>>>
>>> In short, the incremental cost for *ME* to continue supporting the fixes
>>> branches that our customers are using is negligible. There's really no
>>> reason to not do it. It has an additional benefit of making other
>>> Camel users happier by providing more stable releases for them to use.
>>> IMO, it's basically a "win-win" all around, or am I missing something?
>>>
>>> Dan
>>>
>>> On Wednesday, July 06, 2011 7:55:16 AM Christian Schneider wrote:
>>>> Hi Willem,
>>>>
>>>> I can explain a bit from my experience as a user of Camel and CXF at
>>>> my
>>>> former employer regarding patch releases.
>>>>
>>>> We updated our stack every 6 to 8 months. With CXF this mostly simply
>>>> worked. When some bug was detected we could create an issue and help
>>>> fix
>>>> it. It went into the next patch release and we could
>>>> update to this one instead of the feature release.
>>>>
>>>> With Camel it was different. Every new release had a lot of new
>>>> features
>>>> and changes. So we almost every time found a bug in the release that
>>>> prevented us to switch or that was a problem in production that needed
>>>> to be addressed. What went very well in Camel was reporting and fixing
>>>> bugs. I think Camel is probably the project I used where fixes to bugs
>>>> were made fastest. The problem was that the fix was only on trunk.
>>>> Then
>>>> later it was incorporated into the new version. So my first strategy
>>>> was
>>>> to update to the most current camel release when a bug was found and
>>>> fixed. The problem was that we almost every time found another problem
>>>> in the new release.
>>>> So what I did in the end was building our own release with the patches
>>>> to the bugs we had. This worked very well but not every customer wants
>>>> to do this.
>>>>
>>>> Patch releases like 2.7.3 give the customer the fixes they need
>>>> without
>>>> the breaking changes that cause new bugs. So from a customer
>>>> standpoint
>>>> patch releases are very valueable. Of course they make life for us
>>>> more
>>>> complicated so I think we should mostly only support one patch release
>>>> and one feature release at the same time. Of course a company like
>>>> Fuse
>>>> or Talend can also do patch releases on their own but I think it is
>>>> better to have these releases at apache so it is transparent to the
>>>> customer what is in each release and he has no fear of vendor lock in.
>>>>
>>>> Christian
>>>>
>>>> Am 06.07.2011 04:09, schrieb Willem Jiang:
>>>>> Hi Hadrian,
>>>>>
>>>>> I think we are ready for the Camel 2.8.0 release.
>>>>> But I'm not sure why you are still planing to do the patch release
>>>>> for
>>>>> the 2.7.x as we never do this kind small patch release unless it
>>>>> relates to a serious security issue before.
>>>>>
>>>>> Can we just let the people move on to Camel 2.8.0 instead of
>>>>> confusing
>>>>> about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
>>>>>
>>>>> On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
>>>>>> Karaf 2.2.2 is now available and Willem did the upgrade. I think
>>>>>> we
>>>>>> can
>>>>>> get ready to start the release. Are there any other issues that
>>>>>> must
>>>>>> go
>>>>>> into 2.8.0?
>>>>>>
>>>>>> I would also build a 2.7.3 at the same time, there are a few fixes
>>>>>> and
>>>>>> improvements, including some around xmlsecurity.
>>>>>>
>>>>>> Thoughts?
>>>>>> Hadrian
>>>>>>
>>>>>> On 06/30/2011 11:07 PM, Willem Jiang wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I just applied the patch into trunk.
>>>>>>>
>>>>>>> On 7/1/11 12:36 AM, Donald Whytock wrote:
>>>>>>>> https://issues.apache.org/jira/browse/CAMEL-3948
>>>>>>>>
>>>>>>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald
>>>>>>>> Whytock<dw...@gmail.com>
>>>>>>>>
>>>>>>>> wrote:
>>>>>>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the
>>>>>>>>> current
>>>>>>>>> trunk
>>>>>>>>> still needs my final patch.
>>>>>>>>>
>>>>>>>>> Don
>>>>>>>>>
>>>>>>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>>>>>>>>
>>>>>>>>> Onofré<jb...@nanthrax.net> wrote:
>>>>>>>>>> Hi Claus,
>>>>>>>>>>
>>>>>>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies
>>>>>>>>>> yesterday.
>>>>>>>>>> Jamie
>>>>>>>>>> will cut off the release this afternoon.
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> JB
>>>>>>>>>>
>>>>>>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now.
>>>>>>>>>>> There is
>>>>>>>>>>> 2 open
>>>>>>>>>>> tickets.
>>>>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>>>>>>>
>>>>>>>>>>> CAMEL-3774 is about generating the manual and is
>>>>>>>>>>> assigned to
>>>>>>>>>>> Hadrian.
>>>>>>>>>>>
>>>>>>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That
>>>>>>>>>>> release
>>>>>>>>>>> is in
>>>>>>>>>>> progress.
>>>>>>>>>>> So by good chance we should be able to pickup that
>>>>>>>>>>> version
>>>>>>>>>>> when its
>>>>>>>>>>> released.
>>>>>>>>>>> Alternatively we can stick to Karaf 2.2.1 which works
>>>>>>>>>>> fine.
>>>>>>>>>>> (CAMEL-4144 is about some maven validate goal that would
>>>>>>>>>>> require
>>>>>>>>>>> Karaf
>>>>>>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in
>>>>>>>>>>> Karaf
>>>>>>>>>>> is
>>>>>>>>>>> absolutely fine)
>>>>>>>>>>>
>>>>>>>>>>> The CI servers also seems good. Although they tend to
>>>>>>>>>>> run
>>>>>>>>>>> out of
>>>>>>>>>>> memory at the end, such as when testing the examples.
>>>>>>>>>>> But
>>>>>>>>>>> those are
>>>>>>>>>>> the last piece of the build, and thus all components
>>>>>>>>>>> tests
>>>>>>>>>>> fine.
>>>>>>>>>>>
>>>>>>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few
>>>>>>>>>>> spins
>>>>>>>>>>> on
>>>>>>>>>>> the CI
>>>>>>>>>>> servers and then start cutting the Camel 2.8 release.
>>>>>>>>>>> Would
>>>>>>>>>>> be
>>>>>>>>>>> good to
>>>>>>>>>>> get it out before the summer vacation starts. As well
>>>>>>>>>>> its
>>>>>>>>>>> more
>>>>>>>>>>> than 3
>>>>>>>>>>> months since Camel 2.7 was released.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus
>>>>>>>>>>> Ibsen<cl...@gmail.com>
>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>> Hi
>>>>>>>>>>>>
>>>>>>>>>>>> Okay we should really start focusing on getting the
>>>>>>>>>>>> last
>>>>>>>>>>>> tickets
>>>>>>>>>>>> which
>>>>>>>>>>>> has been assigned for 2.8 release done now.
>>>>>>>>>>>> There is about 350 tickets on the roadmap, so its
>>>>>>>>>>>> going to
>>>>>>>>>>>> be the
>>>>>>>>>>>> biggest release, since 2.0 went GA.
>>>>>>>>>>>>
>>>>>>>>>>>> So please take a look at your assigned tickets and get
>>>>>>>>>>>> them
>>>>>>>>>>>> done, or
>>>>>>>>>>>> move them for 2.9.
>>>>>>>>>>>> Then keep eyes on CI servers and help fix any test
>>>>>>>>>>>> failures, so we
>>>>>>>>>>>> have green builds.
>>>>>>>>>>>>
>>>>>>>>>>>> The summer vacation period is approaching so we should
>>>>>>>>>>>> IMHO get
>>>>>>>>>>>> the
>>>>>>>>>>>> 2.8 release out early next month if possible.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian
>>>>>>>>>>>> Zbarcea<hz...@gmail.com>
>>>>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I would propose starting to close down and prepare
>>>>>>>>>>>>> for
>>>>>>>>>>>>> the 2.8.0
>>>>>>>>>>>>> release
>>>>>>>>>>>>> in
>>>>>>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0
>>>>>>>>>>>>> and
>>>>>>>>>>>>> chances are
>>>>>>>>>>>>> will
>>>>>>>>>>>>> be
>>>>>>>>>>>>> over 300 by the release time, probably setting a new
>>>>>>>>>>>>> record.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As of now there are 17 issues unresolved, a few of
>>>>>>>>>>>>> them
>>>>>>>>>>>>> almost
>>>>>>>>>>>>> done, so
>>>>>>>>>>>>> by
>>>>>>>>>>>>> next week I assume there'll be significantly less. I
>>>>>>>>>>>>> would
>>>>>>>>>>>>> suggest
>>>>>>>>>>>>> shifting
>>>>>>>>>>>>> the focus from adding new features to stabilizing
>>>>>>>>>>>>> the
>>>>>>>>>>>>> build. If
>>>>>>>>>>>>> there
>>>>>>>>>>>>> are
>>>>>>>>>>>>> any issues you know of that you think absolutely
>>>>>>>>>>>>> must be
>>>>>>>>>>>>> in 2.8.0
>>>>>>>>>>>>> please
>>>>>>>>>>>>> shout and ask for help if needed (especially non
>>>>>>>>>>>>> committers
>>>>>>>>>>>>> subscribing
>>>>>>>>>>>>> to
>>>>>>>>>>>>> this list).
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hadrian
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Daniel Kulp <dk...@apache.org>.
On Thursday, July 07, 2011 10:40:50 AM Willem Jiang wrote:
> OK, I see the patch rule is based on the Talend customer.
To be clear, I didn't say this is driven by a Talend customer. Again, they
don't care if it's done here or in a private repo or something. However, if
I'm doing some work for a Talend customer, it makes sense to me that everyone
can benefit from it. This can be perfectly applied for Fuse as well. I
know you spend a lot of time porting fixes back to 2.7.x (and 2.6.x, etc...)
for Fuse customers. Other Camel users COULD benefit from that work as well.
That's completely up to you guys though.
Dan
>
> On 7/6/11 9:32 PM, Daniel Kulp wrote:
> > One other note:
> >
> > Talend has customers on 2.7.x that are not likely to move to 2.8.0 any
> > time soon. As Christian pointed out, lots of companies use a 6-8
> > month cycle, Some longer, some shorter, and won't move off what they
> > have for quite a bit of time. Thus, no matter what, I am going to
> > have to port some bug fixes back to 2.7.x. There isn't anyway for me
> > to avoid that (unless I tell my customers "too bad, no fixes" which
> > would not go over well :-) ). I COULD do the porting on some private
> > fork of the Camel branches and deliver the fixes to the customers that
> > way. That's definitely a perfectly valid way to do it. In that case,
> > all my work really would just benefit a small number of Camel users.
> > I'd MUCH MUCH prefer to do the porting here and allow my work to
> > benefit the entire Camel community. It's the exact same amount of
> > work, just in a different place. (well, I suppose if the fork is using
> > git, it could be a little less work as merging with git is so much
> > nicer and faster, but still, that's minor)
> >
> > Likewise for releases. I could create private releases and stick them
> > in a "talend" repository someplace (and in some cases, I may need to do
> > that anyway), but I could also do roughly the same amount of work here
> > (calling the vote is additional work here, but that's minor) and the
> > entire Camel user base benefits. In addition, the releases here would
> > go to central which makes our customers happy. (no Nexus updates,
> > firewall rules updates, etc...)
> >
> > In short, the incremental cost for *ME* to continue supporting the fixes
> > branches that our customers are using is negligible. There's really no
> > reason to not do it. It has an additional benefit of making other
> > Camel users happier by providing more stable releases for them to use.
> > IMO, it's basically a "win-win" all around, or am I missing something?
> >
> > Dan
> >
> > On Wednesday, July 06, 2011 7:55:16 AM Christian Schneider wrote:
> >> Hi Willem,
> >>
> >> I can explain a bit from my experience as a user of Camel and CXF at
> >> my
> >> former employer regarding patch releases.
> >>
> >> We updated our stack every 6 to 8 months. With CXF this mostly simply
> >> worked. When some bug was detected we could create an issue and help
> >> fix
> >> it. It went into the next patch release and we could
> >> update to this one instead of the feature release.
> >>
> >> With Camel it was different. Every new release had a lot of new
> >> features
> >> and changes. So we almost every time found a bug in the release that
> >> prevented us to switch or that was a problem in production that needed
> >> to be addressed. What went very well in Camel was reporting and fixing
> >> bugs. I think Camel is probably the project I used where fixes to bugs
> >> were made fastest. The problem was that the fix was only on trunk.
> >> Then
> >> later it was incorporated into the new version. So my first strategy
> >> was
> >> to update to the most current camel release when a bug was found and
> >> fixed. The problem was that we almost every time found another problem
> >> in the new release.
> >> So what I did in the end was building our own release with the patches
> >> to the bugs we had. This worked very well but not every customer wants
> >> to do this.
> >>
> >> Patch releases like 2.7.3 give the customer the fixes they need
> >> without
> >> the breaking changes that cause new bugs. So from a customer
> >> standpoint
> >> patch releases are very valueable. Of course they make life for us
> >> more
> >> complicated so I think we should mostly only support one patch release
> >> and one feature release at the same time. Of course a company like
> >> Fuse
> >> or Talend can also do patch releases on their own but I think it is
> >> better to have these releases at apache so it is transparent to the
> >> customer what is in each release and he has no fear of vendor lock in.
> >>
> >> Christian
> >>
> >> Am 06.07.2011 04:09, schrieb Willem Jiang:
> >>> Hi Hadrian,
> >>>
> >>> I think we are ready for the Camel 2.8.0 release.
> >>> But I'm not sure why you are still planing to do the patch release
> >>> for
> >>> the 2.7.x as we never do this kind small patch release unless it
> >>> relates to a serious security issue before.
> >>>
> >>> Can we just let the people move on to Camel 2.8.0 instead of
> >>> confusing
> >>> about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
> >>>
> >>> On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
> >>>> Karaf 2.2.2 is now available and Willem did the upgrade. I think
> >>>> we
> >>>> can
> >>>> get ready to start the release. Are there any other issues that
> >>>> must
> >>>> go
> >>>> into 2.8.0?
> >>>>
> >>>> I would also build a 2.7.3 at the same time, there are a few fixes
> >>>> and
> >>>> improvements, including some around xmlsecurity.
> >>>>
> >>>> Thoughts?
> >>>> Hadrian
> >>>>
> >>>> On 06/30/2011 11:07 PM, Willem Jiang wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I just applied the patch into trunk.
> >>>>>
> >>>>> On 7/1/11 12:36 AM, Donald Whytock wrote:
> >>>>>> https://issues.apache.org/jira/browse/CAMEL-3948
> >>>>>>
> >>>>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald
> >>>>>> Whytock<dw...@gmail.com>
> >>>>>>
> >>>>>> wrote:
> >>>>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the
> >>>>>>> current
> >>>>>>> trunk
> >>>>>>> still needs my final patch.
> >>>>>>>
> >>>>>>> Don
> >>>>>>>
> >>>>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
> >>>>>>>
> >>>>>>> Onofré<jb...@nanthrax.net> wrote:
> >>>>>>>> Hi Claus,
> >>>>>>>>
> >>>>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies
> >>>>>>>> yesterday.
> >>>>>>>> Jamie
> >>>>>>>> will cut off the release this afternoon.
> >>>>>>>>
> >>>>>>>> Regards
> >>>>>>>> JB
> >>>>>>>>
> >>>>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
> >>>>>>>>> Hi
> >>>>>>>>>
> >>>>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now.
> >>>>>>>>> There is
> >>>>>>>>> 2 open
> >>>>>>>>> tickets.
> >>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
> >>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
> >>>>>>>>>
> >>>>>>>>> CAMEL-3774 is about generating the manual and is
> >>>>>>>>> assigned to
> >>>>>>>>> Hadrian.
> >>>>>>>>>
> >>>>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That
> >>>>>>>>> release
> >>>>>>>>> is in
> >>>>>>>>> progress.
> >>>>>>>>> So by good chance we should be able to pickup that
> >>>>>>>>> version
> >>>>>>>>> when its
> >>>>>>>>> released.
> >>>>>>>>> Alternatively we can stick to Karaf 2.2.1 which works
> >>>>>>>>> fine.
> >>>>>>>>> (CAMEL-4144 is about some maven validate goal that would
> >>>>>>>>> require
> >>>>>>>>> Karaf
> >>>>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in
> >>>>>>>>> Karaf
> >>>>>>>>> is
> >>>>>>>>> absolutely fine)
> >>>>>>>>>
> >>>>>>>>> The CI servers also seems good. Although they tend to
> >>>>>>>>> run
> >>>>>>>>> out of
> >>>>>>>>> memory at the end, such as when testing the examples.
> >>>>>>>>> But
> >>>>>>>>> those are
> >>>>>>>>> the last piece of the build, and thus all components
> >>>>>>>>> tests
> >>>>>>>>> fine.
> >>>>>>>>>
> >>>>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few
> >>>>>>>>> spins
> >>>>>>>>> on
> >>>>>>>>> the CI
> >>>>>>>>> servers and then start cutting the Camel 2.8 release.
> >>>>>>>>> Would
> >>>>>>>>> be
> >>>>>>>>> good to
> >>>>>>>>> get it out before the summer vacation starts. As well
> >>>>>>>>> its
> >>>>>>>>> more
> >>>>>>>>> than 3
> >>>>>>>>> months since Camel 2.7 was released.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus
> >>>>>>>>> Ibsen<cl...@gmail.com>
> >>>>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>> Hi
> >>>>>>>>>>
> >>>>>>>>>> Okay we should really start focusing on getting the
> >>>>>>>>>> last
> >>>>>>>>>> tickets
> >>>>>>>>>> which
> >>>>>>>>>> has been assigned for 2.8 release done now.
> >>>>>>>>>> There is about 350 tickets on the roadmap, so its
> >>>>>>>>>> going to
> >>>>>>>>>> be the
> >>>>>>>>>> biggest release, since 2.0 went GA.
> >>>>>>>>>>
> >>>>>>>>>> So please take a look at your assigned tickets and get
> >>>>>>>>>> them
> >>>>>>>>>> done, or
> >>>>>>>>>> move them for 2.9.
> >>>>>>>>>> Then keep eyes on CI servers and help fix any test
> >>>>>>>>>> failures, so we
> >>>>>>>>>> have green builds.
> >>>>>>>>>>
> >>>>>>>>>> The summer vacation period is approaching so we should
> >>>>>>>>>> IMHO get
> >>>>>>>>>> the
> >>>>>>>>>> 2.8 release out early next month if possible.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian
> >>>>>>>>>> Zbarcea<hz...@gmail.com>
> >>>>>>>>>>
> >>>>>>>>>> wrote:
> >>>>>>>>>>> Hi,
> >>>>>>>>>>>
> >>>>>>>>>>> I would propose starting to close down and prepare
> >>>>>>>>>>> for
> >>>>>>>>>>> the 2.8.0
> >>>>>>>>>>> release
> >>>>>>>>>>> in
> >>>>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0
> >>>>>>>>>>> and
> >>>>>>>>>>> chances are
> >>>>>>>>>>> will
> >>>>>>>>>>> be
> >>>>>>>>>>> over 300 by the release time, probably setting a new
> >>>>>>>>>>> record.
> >>>>>>>>>>>
> >>>>>>>>>>> As of now there are 17 issues unresolved, a few of
> >>>>>>>>>>> them
> >>>>>>>>>>> almost
> >>>>>>>>>>> done, so
> >>>>>>>>>>> by
> >>>>>>>>>>> next week I assume there'll be significantly less. I
> >>>>>>>>>>> would
> >>>>>>>>>>> suggest
> >>>>>>>>>>> shifting
> >>>>>>>>>>> the focus from adding new features to stabilizing
> >>>>>>>>>>> the
> >>>>>>>>>>> build. If
> >>>>>>>>>>> there
> >>>>>>>>>>> are
> >>>>>>>>>>> any issues you know of that you think absolutely
> >>>>>>>>>>> must be
> >>>>>>>>>>> in 2.8.0
> >>>>>>>>>>> please
> >>>>>>>>>>> shout and ask for help if needed (especially non
> >>>>>>>>>>> committers
> >>>>>>>>>>> subscribing
> >>>>>>>>>>> to
> >>>>>>>>>>> this list).
> >>>>>>>>>>>
> >>>>>>>>>>> Thoughts?
> >>>>>>>>>>>
> >>>>>>>>>>> Hadrian
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Willem Jiang <wi...@gmail.com>.
OK, I see the patch rule is based on the Talend customer.
On 7/6/11 9:32 PM, Daniel Kulp wrote:
>
> One other note:
>
> Talend has customers on 2.7.x that are not likely to move to 2.8.0 any time
> soon. As Christian pointed out, lots of companies use a 6-8 month cycle,
> Some longer, some shorter, and won't move off what they have for quite a bit
> of time. Thus, no matter what, I am going to have to port some bug fixes
> back to 2.7.x. There isn't anyway for me to avoid that (unless I tell my
> customers "too bad, no fixes" which would not go over well :-) ). I COULD do
> the porting on some private fork of the Camel branches and deliver the fixes
> to the customers that way. That's definitely a perfectly valid way to do it.
> In that case, all my work really would just benefit a small number of Camel
> users. I'd MUCH MUCH prefer to do the porting here and allow my work to
> benefit the entire Camel community. It's the exact same amount of work, just
> in a different place. (well, I suppose if the fork is using git, it could be
> a little less work as merging with git is so much nicer and faster, but still,
> that's minor)
>
> Likewise for releases. I could create private releases and stick them in a
> "talend" repository someplace (and in some cases, I may need to do that
> anyway), but I could also do roughly the same amount of work here (calling the
> vote is additional work here, but that's minor) and the entire Camel user base
> benefits. In addition, the releases here would go to central which makes our
> customers happy. (no Nexus updates, firewall rules updates, etc...)
>
> In short, the incremental cost for *ME* to continue supporting the fixes
> branches that our customers are using is negligible. There's really no reason
> to not do it. It has an additional benefit of making other Camel users
> happier by providing more stable releases for them to use. IMO, it's
> basically a "win-win" all around, or am I missing something?
>
> Dan
>
>
>
> On Wednesday, July 06, 2011 7:55:16 AM Christian Schneider wrote:
>> Hi Willem,
>>
>> I can explain a bit from my experience as a user of Camel and CXF at my
>> former employer regarding patch releases.
>>
>> We updated our stack every 6 to 8 months. With CXF this mostly simply
>> worked. When some bug was detected we could create an issue and help fix
>> it. It went into the next patch release and we could
>> update to this one instead of the feature release.
>>
>> With Camel it was different. Every new release had a lot of new features
>> and changes. So we almost every time found a bug in the release that
>> prevented us to switch or that was a problem in production that needed
>> to be addressed. What went very well in Camel was reporting and fixing
>> bugs. I think Camel is probably the project I used where fixes to bugs
>> were made fastest. The problem was that the fix was only on trunk. Then
>> later it was incorporated into the new version. So my first strategy was
>> to update to the most current camel release when a bug was found and
>> fixed. The problem was that we almost every time found another problem
>> in the new release.
>> So what I did in the end was building our own release with the patches
>> to the bugs we had. This worked very well but not every customer wants
>> to do this.
>>
>> Patch releases like 2.7.3 give the customer the fixes they need without
>> the breaking changes that cause new bugs. So from a customer standpoint
>> patch releases are very valueable. Of course they make life for us more
>> complicated so I think we should mostly only support one patch release
>> and one feature release at the same time. Of course a company like Fuse
>> or Talend can also do patch releases on their own but I think it is
>> better to have these releases at apache so it is transparent to the
>> customer what is in each release and he has no fear of vendor lock in.
>>
>> Christian
>>
>> Am 06.07.2011 04:09, schrieb Willem Jiang:
>>> Hi Hadrian,
>>>
>>> I think we are ready for the Camel 2.8.0 release.
>>> But I'm not sure why you are still planing to do the patch release for
>>> the 2.7.x as we never do this kind small patch release unless it
>>> relates to a serious security issue before.
>>>
>>> Can we just let the people move on to Camel 2.8.0 instead of confusing
>>> about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
>>>
>>> On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
>>>> Karaf 2.2.2 is now available and Willem did the upgrade. I think we
>>>> can
>>>> get ready to start the release. Are there any other issues that must
>>>> go
>>>> into 2.8.0?
>>>>
>>>> I would also build a 2.7.3 at the same time, there are a few fixes and
>>>> improvements, including some around xmlsecurity.
>>>>
>>>> Thoughts?
>>>> Hadrian
>>>>
>>>> On 06/30/2011 11:07 PM, Willem Jiang wrote:
>>>>> Hi,
>>>>>
>>>>> I just applied the patch into trunk.
>>>>>
>>>>> On 7/1/11 12:36 AM, Donald Whytock wrote:
>>>>>> https://issues.apache.org/jira/browse/CAMEL-3948
>>>>>>
>>>>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald
>>>>>> Whytock<dw...@gmail.com>
>>>>>>
>>>>>> wrote:
>>>>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current
>>>>>>> trunk
>>>>>>> still needs my final patch.
>>>>>>>
>>>>>>> Don
>>>>>>>
>>>>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>>>>>>
>>>>>>> Onofré<jb...@nanthrax.net> wrote:
>>>>>>>> Hi Claus,
>>>>>>>>
>>>>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies
>>>>>>>> yesterday.
>>>>>>>> Jamie
>>>>>>>> will cut off the release this afternoon.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is
>>>>>>>>> 2 open
>>>>>>>>> tickets.
>>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>>>>>
>>>>>>>>> CAMEL-3774 is about generating the manual and is assigned to
>>>>>>>>> Hadrian.
>>>>>>>>>
>>>>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release
>>>>>>>>> is in
>>>>>>>>> progress.
>>>>>>>>> So by good chance we should be able to pickup that version
>>>>>>>>> when its
>>>>>>>>> released.
>>>>>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>>>>>>> (CAMEL-4144 is about some maven validate goal that would
>>>>>>>>> require
>>>>>>>>> Karaf
>>>>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf
>>>>>>>>> is
>>>>>>>>> absolutely fine)
>>>>>>>>>
>>>>>>>>> The CI servers also seems good. Although they tend to run
>>>>>>>>> out of
>>>>>>>>> memory at the end, such as when testing the examples. But
>>>>>>>>> those are
>>>>>>>>> the last piece of the build, and thus all components tests
>>>>>>>>> fine.
>>>>>>>>>
>>>>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins
>>>>>>>>> on
>>>>>>>>> the CI
>>>>>>>>> servers and then start cutting the Camel 2.8 release. Would
>>>>>>>>> be
>>>>>>>>> good to
>>>>>>>>> get it out before the summer vacation starts. As well its
>>>>>>>>> more
>>>>>>>>> than 3
>>>>>>>>> months since Camel 2.7 was released.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus
>>>>>>>>> Ibsen<cl...@gmail.com>
>>>>>>>>>
>>>>>>>>> wrote:
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> Okay we should really start focusing on getting the last
>>>>>>>>>> tickets
>>>>>>>>>> which
>>>>>>>>>> has been assigned for 2.8 release done now.
>>>>>>>>>> There is about 350 tickets on the roadmap, so its going to
>>>>>>>>>> be the
>>>>>>>>>> biggest release, since 2.0 went GA.
>>>>>>>>>>
>>>>>>>>>> So please take a look at your assigned tickets and get
>>>>>>>>>> them
>>>>>>>>>> done, or
>>>>>>>>>> move them for 2.9.
>>>>>>>>>> Then keep eyes on CI servers and help fix any test
>>>>>>>>>> failures, so we
>>>>>>>>>> have green builds.
>>>>>>>>>>
>>>>>>>>>> The summer vacation period is approaching so we should
>>>>>>>>>> IMHO get
>>>>>>>>>> the
>>>>>>>>>> 2.8 release out early next month if possible.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian
>>>>>>>>>> Zbarcea<hz...@gmail.com>
>>>>>>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I would propose starting to close down and prepare for
>>>>>>>>>>> the 2.8.0
>>>>>>>>>>> release
>>>>>>>>>>> in
>>>>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and
>>>>>>>>>>> chances are
>>>>>>>>>>> will
>>>>>>>>>>> be
>>>>>>>>>>> over 300 by the release time, probably setting a new
>>>>>>>>>>> record.
>>>>>>>>>>>
>>>>>>>>>>> As of now there are 17 issues unresolved, a few of them
>>>>>>>>>>> almost
>>>>>>>>>>> done, so
>>>>>>>>>>> by
>>>>>>>>>>> next week I assume there'll be significantly less. I
>>>>>>>>>>> would
>>>>>>>>>>> suggest
>>>>>>>>>>> shifting
>>>>>>>>>>> the focus from adding new features to stabilizing the
>>>>>>>>>>> build. If
>>>>>>>>>>> there
>>>>>>>>>>> are
>>>>>>>>>>> any issues you know of that you think absolutely must be
>>>>>>>>>>> in 2.8.0
>>>>>>>>>>> please
>>>>>>>>>>> shout and ask for help if needed (especially non
>>>>>>>>>>> committers
>>>>>>>>>>> subscribing
>>>>>>>>>>> to
>>>>>>>>>>> this list).
>>>>>>>>>>>
>>>>>>>>>>> Thoughts?
>>>>>>>>>>>
>>>>>>>>>>> Hadrian
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Daniel Kulp <dk...@apache.org>.
One other note:
Talend has customers on 2.7.x that are not likely to move to 2.8.0 any time
soon. As Christian pointed out, lots of companies use a 6-8 month cycle,
Some longer, some shorter, and won't move off what they have for quite a bit
of time. Thus, no matter what, I am going to have to port some bug fixes
back to 2.7.x. There isn't anyway for me to avoid that (unless I tell my
customers "too bad, no fixes" which would not go over well :-) ). I COULD do
the porting on some private fork of the Camel branches and deliver the fixes
to the customers that way. That's definitely a perfectly valid way to do it.
In that case, all my work really would just benefit a small number of Camel
users. I'd MUCH MUCH prefer to do the porting here and allow my work to
benefit the entire Camel community. It's the exact same amount of work, just
in a different place. (well, I suppose if the fork is using git, it could be
a little less work as merging with git is so much nicer and faster, but still,
that's minor)
Likewise for releases. I could create private releases and stick them in a
"talend" repository someplace (and in some cases, I may need to do that
anyway), but I could also do roughly the same amount of work here (calling the
vote is additional work here, but that's minor) and the entire Camel user base
benefits. In addition, the releases here would go to central which makes our
customers happy. (no Nexus updates, firewall rules updates, etc...)
In short, the incremental cost for *ME* to continue supporting the fixes
branches that our customers are using is negligible. There's really no reason
to not do it. It has an additional benefit of making other Camel users
happier by providing more stable releases for them to use. IMO, it's
basically a "win-win" all around, or am I missing something?
Dan
On Wednesday, July 06, 2011 7:55:16 AM Christian Schneider wrote:
> Hi Willem,
>
> I can explain a bit from my experience as a user of Camel and CXF at my
> former employer regarding patch releases.
>
> We updated our stack every 6 to 8 months. With CXF this mostly simply
> worked. When some bug was detected we could create an issue and help fix
> it. It went into the next patch release and we could
> update to this one instead of the feature release.
>
> With Camel it was different. Every new release had a lot of new features
> and changes. So we almost every time found a bug in the release that
> prevented us to switch or that was a problem in production that needed
> to be addressed. What went very well in Camel was reporting and fixing
> bugs. I think Camel is probably the project I used where fixes to bugs
> were made fastest. The problem was that the fix was only on trunk. Then
> later it was incorporated into the new version. So my first strategy was
> to update to the most current camel release when a bug was found and
> fixed. The problem was that we almost every time found another problem
> in the new release.
> So what I did in the end was building our own release with the patches
> to the bugs we had. This worked very well but not every customer wants
> to do this.
>
> Patch releases like 2.7.3 give the customer the fixes they need without
> the breaking changes that cause new bugs. So from a customer standpoint
> patch releases are very valueable. Of course they make life for us more
> complicated so I think we should mostly only support one patch release
> and one feature release at the same time. Of course a company like Fuse
> or Talend can also do patch releases on their own but I think it is
> better to have these releases at apache so it is transparent to the
> customer what is in each release and he has no fear of vendor lock in.
>
> Christian
>
> Am 06.07.2011 04:09, schrieb Willem Jiang:
> > Hi Hadrian,
> >
> > I think we are ready for the Camel 2.8.0 release.
> > But I'm not sure why you are still planing to do the patch release for
> > the 2.7.x as we never do this kind small patch release unless it
> > relates to a serious security issue before.
> >
> > Can we just let the people move on to Camel 2.8.0 instead of confusing
> > about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
> >
> > On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
> >> Karaf 2.2.2 is now available and Willem did the upgrade. I think we
> >> can
> >> get ready to start the release. Are there any other issues that must
> >> go
> >> into 2.8.0?
> >>
> >> I would also build a 2.7.3 at the same time, there are a few fixes and
> >> improvements, including some around xmlsecurity.
> >>
> >> Thoughts?
> >> Hadrian
> >>
> >> On 06/30/2011 11:07 PM, Willem Jiang wrote:
> >>> Hi,
> >>>
> >>> I just applied the patch into trunk.
> >>>
> >>> On 7/1/11 12:36 AM, Donald Whytock wrote:
> >>>> https://issues.apache.org/jira/browse/CAMEL-3948
> >>>>
> >>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald
> >>>> Whytock<dw...@gmail.com>
> >>>>
> >>>> wrote:
> >>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current
> >>>>> trunk
> >>>>> still needs my final patch.
> >>>>>
> >>>>> Don
> >>>>>
> >>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
> >>>>>
> >>>>> Onofré<jb...@nanthrax.net> wrote:
> >>>>>> Hi Claus,
> >>>>>>
> >>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies
> >>>>>> yesterday.
> >>>>>> Jamie
> >>>>>> will cut off the release this afternoon.
> >>>>>>
> >>>>>> Regards
> >>>>>> JB
> >>>>>>
> >>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
> >>>>>>> Hi
> >>>>>>>
> >>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is
> >>>>>>> 2 open
> >>>>>>> tickets.
> >>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
> >>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
> >>>>>>>
> >>>>>>> CAMEL-3774 is about generating the manual and is assigned to
> >>>>>>> Hadrian.
> >>>>>>>
> >>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release
> >>>>>>> is in
> >>>>>>> progress.
> >>>>>>> So by good chance we should be able to pickup that version
> >>>>>>> when its
> >>>>>>> released.
> >>>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
> >>>>>>> (CAMEL-4144 is about some maven validate goal that would
> >>>>>>> require
> >>>>>>> Karaf
> >>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf
> >>>>>>> is
> >>>>>>> absolutely fine)
> >>>>>>>
> >>>>>>> The CI servers also seems good. Although they tend to run
> >>>>>>> out of
> >>>>>>> memory at the end, such as when testing the examples. But
> >>>>>>> those are
> >>>>>>> the last piece of the build, and thus all components tests
> >>>>>>> fine.
> >>>>>>>
> >>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins
> >>>>>>> on
> >>>>>>> the CI
> >>>>>>> servers and then start cutting the Camel 2.8 release. Would
> >>>>>>> be
> >>>>>>> good to
> >>>>>>> get it out before the summer vacation starts. As well its
> >>>>>>> more
> >>>>>>> than 3
> >>>>>>> months since Camel 2.7 was released.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus
> >>>>>>> Ibsen<cl...@gmail.com>
> >>>>>>>
> >>>>>>> wrote:
> >>>>>>>> Hi
> >>>>>>>>
> >>>>>>>> Okay we should really start focusing on getting the last
> >>>>>>>> tickets
> >>>>>>>> which
> >>>>>>>> has been assigned for 2.8 release done now.
> >>>>>>>> There is about 350 tickets on the roadmap, so its going to
> >>>>>>>> be the
> >>>>>>>> biggest release, since 2.0 went GA.
> >>>>>>>>
> >>>>>>>> So please take a look at your assigned tickets and get
> >>>>>>>> them
> >>>>>>>> done, or
> >>>>>>>> move them for 2.9.
> >>>>>>>> Then keep eyes on CI servers and help fix any test
> >>>>>>>> failures, so we
> >>>>>>>> have green builds.
> >>>>>>>>
> >>>>>>>> The summer vacation period is approaching so we should
> >>>>>>>> IMHO get
> >>>>>>>> the
> >>>>>>>> 2.8 release out early next month if possible.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian
> >>>>>>>> Zbarcea<hz...@gmail.com>
> >>>>>>>>
> >>>>>>>> wrote:
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> I would propose starting to close down and prepare for
> >>>>>>>>> the 2.8.0
> >>>>>>>>> release
> >>>>>>>>> in
> >>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and
> >>>>>>>>> chances are
> >>>>>>>>> will
> >>>>>>>>> be
> >>>>>>>>> over 300 by the release time, probably setting a new
> >>>>>>>>> record.
> >>>>>>>>>
> >>>>>>>>> As of now there are 17 issues unresolved, a few of them
> >>>>>>>>> almost
> >>>>>>>>> done, so
> >>>>>>>>> by
> >>>>>>>>> next week I assume there'll be significantly less. I
> >>>>>>>>> would
> >>>>>>>>> suggest
> >>>>>>>>> shifting
> >>>>>>>>> the focus from adding new features to stabilizing the
> >>>>>>>>> build. If
> >>>>>>>>> there
> >>>>>>>>> are
> >>>>>>>>> any issues you know of that you think absolutely must be
> >>>>>>>>> in 2.8.0
> >>>>>>>>> please
> >>>>>>>>> shout and ask for help if needed (especially non
> >>>>>>>>> committers
> >>>>>>>>> subscribing
> >>>>>>>>> to
> >>>>>>>>> this list).
> >>>>>>>>>
> >>>>>>>>> Thoughts?
> >>>>>>>>>
> >>>>>>>>> Hadrian
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: [DISCUSS] Closing down for the 2.8.0/2.7.3 release
Posted by Daniel Kulp <dk...@apache.org>.
On a related note, 2.7.3 is looking to be in very good shape as well. I've
merged back over 60 bug fixes and things are looking pretty good. There are
some more bug fixes that could get merged back, but it's probably a good idea
to get what's there out and do that for 2.7.4.
I currently have a single test failure in camel-spring, but looking into it,
it's a test case merged back that requires some of the improvements in 2.8 so
I'll likely just @Ignore it.
In any case, I'll likely do the build tomorrow (and let the votes then run
till Monday or Tuesday) unless someone pops up with a major thing they'd like
addressed in 2.7.3 first.
Dan
On Tuesday, July 12, 2011 3:25:45 PM Claus Ibsen wrote:
> Hi
>
> So Camel 2.8.0 starts to look good.
>
> The last CI test at Apache had only 1 unit test failure which is a non
> deterministic test that can fail for some strange reason.
> https://builds.apache.org/job/Camel.trunk.fulltest/366/
>
> I also ran a local OSGi unit test this morning and they all passed.
>
> In terms of ticket outstanding in JIRA then there is only 2 left
> https://issues.apache.org/jira/browse/CAMEL-3774
> https://issues.apache.org/jira/browse/CAMEL-4189
>
> 3774: This is about generating the manual when doing the release. I
> guess Hadrian haven't had a look at it. Since we are able to cut the
> release, I guess this ticket may be able to postpone for Camel 2.9
>
> 4189: This is about a config.properties in the karaf. As I understand
> this config.properties file is not part of the release in the kit or
> in the maven repository. Its used for the karaf validate plugin, to
> validate the features.xml file. Correct me if I am wrong. This could
> be post poned to Camel 2.9.
>
> So from a JIRA point of view it seems good. Do anyone have any last
> item tickets they would like addressed?
>
> I have two tickets which we can discuss whether we want to delay the
> release to get included
> https://issues.apache.org/jira/browse/CAMEL-4212
> https://issues.apache.org/jira/browse/CAMEL-4202
>
> 4212 is about supporting multi value headers in the HTTP related
> components. This may be a bit more work, so we may consider scheduling
> this for Camel 2.9. This is discussed on the @dev forum.
>
> 4202 is being discussed on the @user forum. Its about making
> request/reply over JMS with fixed replyTo queues faster. It could be
> worthwhile for the ppl who uses JMS to participate in the @user
> discussion so we are able to agree upon some solution.
>
> On Fri, Jul 8, 2011 at 10:53 AM, Claus Ibsen <cl...@gmail.com> wrote:
> > Hi
> >
> > I just ran the osgi tests locally and stumbled across two issues
> >
> > 1)
> > Some weird maven duplicate test set issue about FtpConsumerTest. So I
> > disable that test to move on. I know the tests works fine when running
> > it manually, eg from an IDE etc. Anyway the globe keep on turning and
> > we can't be stuck fiddling with weird maven issues all day.
> >
> > 2)
> > The MailRouteTest no longer works. I guess its due those recent
> > changes in the Camel karaf feature.xml file. So I disabled the test.
> > The test relies on that there is a Mocked JavaMail provider installed,
> > that can act as the mail server. But it doesn't so it tries to connect
> > to a local running mail server on port 25.
> >
> > All the other tests passed.
> >
> > So lets close down this baby so we can cut a release for an overdue
> > release. We owe it to the community to bring out Camel 2.8.0 this
> > summer :)
> >
> > --
> > Claus Ibsen
> > -----------------
> > FuseSource
> > Email: cibsen@fusesource.com
> > Web: http://fusesource.com
> > Twitter: davsclaus, fusenews
> > Blog: http://davsclaus.blogspot.com/
> > Author of Camel in Action: http://www.manning.com/ibsen/
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Jul 13, 2011 at 3:48 PM, Claus Ibsen <cl...@gmail.com> wrote:
> On Wed, Jul 13, 2011 at 3:22 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
>> I am ready to start the 2.8.0 builds in about one hour. If you know of
>> anything that still needs to be fixed please let me know asap.
>>
>
> I will commit a fix for
> https://issues.apache.org/jira/browse/CAMEL-4222 in about 30 min when
> the full unit test is complete.
I have committed the fix.
>
>
>> Cheers,
>> Hadrian
>>
>>
>> On 07/12/2011 11:03 PM, Hadrian Zbarcea wrote:
>>>
>>> I reviewed your patch and it looks ok, plus the change is pretty
>>> isolated. If that's the only thing left to be done, please go ahead and
>>> commit it. I started a fresh build over night. If all goes well, I'll
>>> start building the 2.8.0 release in the morning.
>>>
>>> Hadrian
>>>
>>>
>>> On 07/12/2011 04:00 PM, Richard Kettelerij wrote:
>>>>
>>>> I doubt if it would be wise to stall the release much longer. In terms of
>>>> the number of tickets, 2.8.0 seems to be the biggest release yet. Also on
>>>> June 9 Hadrian proposed to cut the release in 2-3 weeks, it's now over 4
>>>> weeks since that post so the release is already a bit overdue.
>>>>
>>>> Nevertheless, would anyone what to see
>>>> https://issues.apache.org/jira/browse/CAMEL-4093 included? I attached a
>>>> patch a couple of weeks ago. It's not a big change and ready to be
>>>> committed, but I have no problem with postponing it for 2.9.0.
>>>>
>>>> On Tue, Jul 12, 2011 at 3:25 PM, Claus Ibsen<cl...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> So Camel 2.8.0 starts to look good.
>>>>>
>>>>> The last CI test at Apache had only 1 unit test failure which is a non
>>>>> deterministic test that can fail for some strange reason.
>>>>> https://builds.apache.org/job/Camel.trunk.fulltest/366/
>>>>>
>>>>> I also ran a local OSGi unit test this morning and they all passed.
>>>>>
>>>>> In terms of ticket outstanding in JIRA then there is only 2 left
>>>>> https://issues.apache.org/jira/browse/CAMEL-3774
>>>>> https://issues.apache.org/jira/browse/CAMEL-4189
>>>>>
>>>>> 3774: This is about generating the manual when doing the release. I
>>>>> guess Hadrian haven't had a look at it. Since we are able to cut the
>>>>> release, I guess this ticket may be able to postpone for Camel 2.9
>>>>>
>>>>> 4189: This is about a config.properties in the karaf. As I understand
>>>>> this config.properties file is not part of the release in the kit or
>>>>> in the maven repository. Its used for the karaf validate plugin, to
>>>>> validate the features.xml file. Correct me if I am wrong. This could
>>>>> be post poned to Camel 2.9.
>>>>>
>>>>> So from a JIRA point of view it seems good. Do anyone have any last
>>>>> item tickets they would like addressed?
>>>>>
>>>>> I have two tickets which we can discuss whether we want to delay the
>>>>> release to get included
>>>>> https://issues.apache.org/jira/browse/CAMEL-4212
>>>>> https://issues.apache.org/jira/browse/CAMEL-4202
>>>>>
>>>>> 4212 is about supporting multi value headers in the HTTP related
>>>>> components. This may be a bit more work, so we may consider scheduling
>>>>> this for Camel 2.9. This is discussed on the @dev forum.
>>>>>
>>>>> 4202 is being discussed on the @user forum. Its about making
>>>>> request/reply over JMS with fixed replyTo queues faster. It could be
>>>>> worthwhile for the ppl who uses JMS to participate in the @user
>>>>> discussion so we are able to agree upon some solution.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jul 8, 2011 at 10:53 AM, Claus Ibsen<cl...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> I just ran the osgi tests locally and stumbled across two issues
>>>>>>
>>>>>> 1)
>>>>>> Some weird maven duplicate test set issue about FtpConsumerTest. So I
>>>>>> disable that test to move on. I know the tests works fine when running
>>>>>> it manually, eg from an IDE etc. Anyway the globe keep on turning and
>>>>>> we can't be stuck fiddling with weird maven issues all day.
>>>>>>
>>>>>> 2)
>>>>>> The MailRouteTest no longer works. I guess its due those recent
>>>>>> changes in the Camel karaf feature.xml file. So I disabled the test.
>>>>>> The test relies on that there is a Mocked JavaMail provider installed,
>>>>>> that can act as the mail server. But it doesn't so it tries to connect
>>>>>> to a local running mail server on port 25.
>>>>>>
>>>>>> All the other tests passed.
>>>>>>
>>>>>> So lets close down this baby so we can cut a release for an overdue
>>>>>> release. We owe it to the community to bring out Camel 2.8.0 this
>>>>>> summer :)
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> FuseSource
>>>>>> Email: cibsen@fusesource.com
>>>>>> Web: http://fusesource.com
>>>>>> Twitter: davsclaus, fusenews
>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> FuseSource
>>>>> Email: cibsen@fusesource.com
>>>>> Web: http://fusesource.com
>>>>> Twitter: davsclaus, fusenews
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>
>>>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Jul 13, 2011 at 3:22 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> I am ready to start the 2.8.0 builds in about one hour. If you know of
> anything that still needs to be fixed please let me know asap.
>
I will commit a fix for
https://issues.apache.org/jira/browse/CAMEL-4222 in about 30 min when
the full unit test is complete.
> Cheers,
> Hadrian
>
>
> On 07/12/2011 11:03 PM, Hadrian Zbarcea wrote:
>>
>> I reviewed your patch and it looks ok, plus the change is pretty
>> isolated. If that's the only thing left to be done, please go ahead and
>> commit it. I started a fresh build over night. If all goes well, I'll
>> start building the 2.8.0 release in the morning.
>>
>> Hadrian
>>
>>
>> On 07/12/2011 04:00 PM, Richard Kettelerij wrote:
>>>
>>> I doubt if it would be wise to stall the release much longer. In terms of
>>> the number of tickets, 2.8.0 seems to be the biggest release yet. Also on
>>> June 9 Hadrian proposed to cut the release in 2-3 weeks, it's now over 4
>>> weeks since that post so the release is already a bit overdue.
>>>
>>> Nevertheless, would anyone what to see
>>> https://issues.apache.org/jira/browse/CAMEL-4093 included? I attached a
>>> patch a couple of weeks ago. It's not a big change and ready to be
>>> committed, but I have no problem with postponing it for 2.9.0.
>>>
>>> On Tue, Jul 12, 2011 at 3:25 PM, Claus Ibsen<cl...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> So Camel 2.8.0 starts to look good.
>>>>
>>>> The last CI test at Apache had only 1 unit test failure which is a non
>>>> deterministic test that can fail for some strange reason.
>>>> https://builds.apache.org/job/Camel.trunk.fulltest/366/
>>>>
>>>> I also ran a local OSGi unit test this morning and they all passed.
>>>>
>>>> In terms of ticket outstanding in JIRA then there is only 2 left
>>>> https://issues.apache.org/jira/browse/CAMEL-3774
>>>> https://issues.apache.org/jira/browse/CAMEL-4189
>>>>
>>>> 3774: This is about generating the manual when doing the release. I
>>>> guess Hadrian haven't had a look at it. Since we are able to cut the
>>>> release, I guess this ticket may be able to postpone for Camel 2.9
>>>>
>>>> 4189: This is about a config.properties in the karaf. As I understand
>>>> this config.properties file is not part of the release in the kit or
>>>> in the maven repository. Its used for the karaf validate plugin, to
>>>> validate the features.xml file. Correct me if I am wrong. This could
>>>> be post poned to Camel 2.9.
>>>>
>>>> So from a JIRA point of view it seems good. Do anyone have any last
>>>> item tickets they would like addressed?
>>>>
>>>> I have two tickets which we can discuss whether we want to delay the
>>>> release to get included
>>>> https://issues.apache.org/jira/browse/CAMEL-4212
>>>> https://issues.apache.org/jira/browse/CAMEL-4202
>>>>
>>>> 4212 is about supporting multi value headers in the HTTP related
>>>> components. This may be a bit more work, so we may consider scheduling
>>>> this for Camel 2.9. This is discussed on the @dev forum.
>>>>
>>>> 4202 is being discussed on the @user forum. Its about making
>>>> request/reply over JMS with fixed replyTo queues faster. It could be
>>>> worthwhile for the ppl who uses JMS to participate in the @user
>>>> discussion so we are able to agree upon some solution.
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Jul 8, 2011 at 10:53 AM, Claus Ibsen<cl...@gmail.com>
>>>> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> I just ran the osgi tests locally and stumbled across two issues
>>>>>
>>>>> 1)
>>>>> Some weird maven duplicate test set issue about FtpConsumerTest. So I
>>>>> disable that test to move on. I know the tests works fine when running
>>>>> it manually, eg from an IDE etc. Anyway the globe keep on turning and
>>>>> we can't be stuck fiddling with weird maven issues all day.
>>>>>
>>>>> 2)
>>>>> The MailRouteTest no longer works. I guess its due those recent
>>>>> changes in the Camel karaf feature.xml file. So I disabled the test.
>>>>> The test relies on that there is a Mocked JavaMail provider installed,
>>>>> that can act as the mail server. But it doesn't so it tries to connect
>>>>> to a local running mail server on port 25.
>>>>>
>>>>> All the other tests passed.
>>>>>
>>>>> So lets close down this baby so we can cut a release for an overdue
>>>>> release. We owe it to the community to bring out Camel 2.8.0 this
>>>>> summer :)
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> FuseSource
>>>>> Email: cibsen@fusesource.com
>>>>> Web: http://fusesource.com
>>>>> Twitter: davsclaus, fusenews
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> FuseSource
>>>> Email: cibsen@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>
>>>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I am ready to start the 2.8.0 builds in about one hour. If you know of
anything that still needs to be fixed please let me know asap.
Cheers,
Hadrian
On 07/12/2011 11:03 PM, Hadrian Zbarcea wrote:
> I reviewed your patch and it looks ok, plus the change is pretty
> isolated. If that's the only thing left to be done, please go ahead and
> commit it. I started a fresh build over night. If all goes well, I'll
> start building the 2.8.0 release in the morning.
>
> Hadrian
>
>
> On 07/12/2011 04:00 PM, Richard Kettelerij wrote:
>> I doubt if it would be wise to stall the release much longer. In terms of
>> the number of tickets, 2.8.0 seems to be the biggest release yet. Also on
>> June 9 Hadrian proposed to cut the release in 2-3 weeks, it's now over 4
>> weeks since that post so the release is already a bit overdue.
>>
>> Nevertheless, would anyone what to see
>> https://issues.apache.org/jira/browse/CAMEL-4093 included? I attached a
>> patch a couple of weeks ago. It's not a big change and ready to be
>> committed, but I have no problem with postponing it for 2.9.0.
>>
>> On Tue, Jul 12, 2011 at 3:25 PM, Claus Ibsen<cl...@gmail.com>
>> wrote:
>>
>>> Hi
>>>
>>> So Camel 2.8.0 starts to look good.
>>>
>>> The last CI test at Apache had only 1 unit test failure which is a non
>>> deterministic test that can fail for some strange reason.
>>> https://builds.apache.org/job/Camel.trunk.fulltest/366/
>>>
>>> I also ran a local OSGi unit test this morning and they all passed.
>>>
>>> In terms of ticket outstanding in JIRA then there is only 2 left
>>> https://issues.apache.org/jira/browse/CAMEL-3774
>>> https://issues.apache.org/jira/browse/CAMEL-4189
>>>
>>> 3774: This is about generating the manual when doing the release. I
>>> guess Hadrian haven't had a look at it. Since we are able to cut the
>>> release, I guess this ticket may be able to postpone for Camel 2.9
>>>
>>> 4189: This is about a config.properties in the karaf. As I understand
>>> this config.properties file is not part of the release in the kit or
>>> in the maven repository. Its used for the karaf validate plugin, to
>>> validate the features.xml file. Correct me if I am wrong. This could
>>> be post poned to Camel 2.9.
>>>
>>> So from a JIRA point of view it seems good. Do anyone have any last
>>> item tickets they would like addressed?
>>>
>>> I have two tickets which we can discuss whether we want to delay the
>>> release to get included
>>> https://issues.apache.org/jira/browse/CAMEL-4212
>>> https://issues.apache.org/jira/browse/CAMEL-4202
>>>
>>> 4212 is about supporting multi value headers in the HTTP related
>>> components. This may be a bit more work, so we may consider scheduling
>>> this for Camel 2.9. This is discussed on the @dev forum.
>>>
>>> 4202 is being discussed on the @user forum. Its about making
>>> request/reply over JMS with fixed replyTo queues faster. It could be
>>> worthwhile for the ppl who uses JMS to participate in the @user
>>> discussion so we are able to agree upon some solution.
>>>
>>>
>>>
>>>
>>> On Fri, Jul 8, 2011 at 10:53 AM, Claus Ibsen<cl...@gmail.com>
>>> wrote:
>>>> Hi
>>>>
>>>> I just ran the osgi tests locally and stumbled across two issues
>>>>
>>>> 1)
>>>> Some weird maven duplicate test set issue about FtpConsumerTest. So I
>>>> disable that test to move on. I know the tests works fine when running
>>>> it manually, eg from an IDE etc. Anyway the globe keep on turning and
>>>> we can't be stuck fiddling with weird maven issues all day.
>>>>
>>>> 2)
>>>> The MailRouteTest no longer works. I guess its due those recent
>>>> changes in the Camel karaf feature.xml file. So I disabled the test.
>>>> The test relies on that there is a Mocked JavaMail provider installed,
>>>> that can act as the mail server. But it doesn't so it tries to connect
>>>> to a local running mail server on port 25.
>>>>
>>>> All the other tests passed.
>>>>
>>>> So lets close down this baby so we can cut a release for an overdue
>>>> release. We owe it to the community to bring out Camel 2.8.0 this
>>>> summer :)
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> FuseSource
>>>> Email: cibsen@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>
>>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I reviewed your patch and it looks ok, plus the change is pretty
isolated. If that's the only thing left to be done, please go ahead and
commit it. I started a fresh build over night. If all goes well, I'll
start building the 2.8.0 release in the morning.
Hadrian
On 07/12/2011 04:00 PM, Richard Kettelerij wrote:
> I doubt if it would be wise to stall the release much longer. In terms of
> the number of tickets, 2.8.0 seems to be the biggest release yet. Also on
> June 9 Hadrian proposed to cut the release in 2-3 weeks, it's now over 4
> weeks since that post so the release is already a bit overdue.
>
> Nevertheless, would anyone what to see
> https://issues.apache.org/jira/browse/CAMEL-4093 included? I attached a
> patch a couple of weeks ago. It's not a big change and ready to be
> committed, but I have no problem with postponing it for 2.9.0.
>
> On Tue, Jul 12, 2011 at 3:25 PM, Claus Ibsen<cl...@gmail.com> wrote:
>
>> Hi
>>
>> So Camel 2.8.0 starts to look good.
>>
>> The last CI test at Apache had only 1 unit test failure which is a non
>> deterministic test that can fail for some strange reason.
>> https://builds.apache.org/job/Camel.trunk.fulltest/366/
>>
>> I also ran a local OSGi unit test this morning and they all passed.
>>
>> In terms of ticket outstanding in JIRA then there is only 2 left
>> https://issues.apache.org/jira/browse/CAMEL-3774
>> https://issues.apache.org/jira/browse/CAMEL-4189
>>
>> 3774: This is about generating the manual when doing the release. I
>> guess Hadrian haven't had a look at it. Since we are able to cut the
>> release, I guess this ticket may be able to postpone for Camel 2.9
>>
>> 4189: This is about a config.properties in the karaf. As I understand
>> this config.properties file is not part of the release in the kit or
>> in the maven repository. Its used for the karaf validate plugin, to
>> validate the features.xml file. Correct me if I am wrong. This could
>> be post poned to Camel 2.9.
>>
>> So from a JIRA point of view it seems good. Do anyone have any last
>> item tickets they would like addressed?
>>
>> I have two tickets which we can discuss whether we want to delay the
>> release to get included
>> https://issues.apache.org/jira/browse/CAMEL-4212
>> https://issues.apache.org/jira/browse/CAMEL-4202
>>
>> 4212 is about supporting multi value headers in the HTTP related
>> components. This may be a bit more work, so we may consider scheduling
>> this for Camel 2.9. This is discussed on the @dev forum.
>>
>> 4202 is being discussed on the @user forum. Its about making
>> request/reply over JMS with fixed replyTo queues faster. It could be
>> worthwhile for the ppl who uses JMS to participate in the @user
>> discussion so we are able to agree upon some solution.
>>
>>
>>
>>
>> On Fri, Jul 8, 2011 at 10:53 AM, Claus Ibsen<cl...@gmail.com>
>> wrote:
>>> Hi
>>>
>>> I just ran the osgi tests locally and stumbled across two issues
>>>
>>> 1)
>>> Some weird maven duplicate test set issue about FtpConsumerTest. So I
>>> disable that test to move on. I know the tests works fine when running
>>> it manually, eg from an IDE etc. Anyway the globe keep on turning and
>>> we can't be stuck fiddling with weird maven issues all day.
>>>
>>> 2)
>>> The MailRouteTest no longer works. I guess its due those recent
>>> changes in the Camel karaf feature.xml file. So I disabled the test.
>>> The test relies on that there is a Mocked JavaMail provider installed,
>>> that can act as the mail server. But it doesn't so it tries to connect
>>> to a local running mail server on port 25.
>>>
>>> All the other tests passed.
>>>
>>> So lets close down this baby so we can cut a release for an overdue
>>> release. We owe it to the community to bring out Camel 2.8.0 this
>>> summer :)
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Richard Kettelerij <ri...@gmail.com>.
I doubt if it would be wise to stall the release much longer. In terms of
the number of tickets, 2.8.0 seems to be the biggest release yet. Also on
June 9 Hadrian proposed to cut the release in 2-3 weeks, it's now over 4
weeks since that post so the release is already a bit overdue.
Nevertheless, would anyone what to see
https://issues.apache.org/jira/browse/CAMEL-4093 included? I attached a
patch a couple of weeks ago. It's not a big change and ready to be
committed, but I have no problem with postponing it for 2.9.0.
On Tue, Jul 12, 2011 at 3:25 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> So Camel 2.8.0 starts to look good.
>
> The last CI test at Apache had only 1 unit test failure which is a non
> deterministic test that can fail for some strange reason.
> https://builds.apache.org/job/Camel.trunk.fulltest/366/
>
> I also ran a local OSGi unit test this morning and they all passed.
>
> In terms of ticket outstanding in JIRA then there is only 2 left
> https://issues.apache.org/jira/browse/CAMEL-3774
> https://issues.apache.org/jira/browse/CAMEL-4189
>
> 3774: This is about generating the manual when doing the release. I
> guess Hadrian haven't had a look at it. Since we are able to cut the
> release, I guess this ticket may be able to postpone for Camel 2.9
>
> 4189: This is about a config.properties in the karaf. As I understand
> this config.properties file is not part of the release in the kit or
> in the maven repository. Its used for the karaf validate plugin, to
> validate the features.xml file. Correct me if I am wrong. This could
> be post poned to Camel 2.9.
>
> So from a JIRA point of view it seems good. Do anyone have any last
> item tickets they would like addressed?
>
> I have two tickets which we can discuss whether we want to delay the
> release to get included
> https://issues.apache.org/jira/browse/CAMEL-4212
> https://issues.apache.org/jira/browse/CAMEL-4202
>
> 4212 is about supporting multi value headers in the HTTP related
> components. This may be a bit more work, so we may consider scheduling
> this for Camel 2.9. This is discussed on the @dev forum.
>
> 4202 is being discussed on the @user forum. Its about making
> request/reply over JMS with fixed replyTo queues faster. It could be
> worthwhile for the ppl who uses JMS to participate in the @user
> discussion so we are able to agree upon some solution.
>
>
>
>
> On Fri, Jul 8, 2011 at 10:53 AM, Claus Ibsen <cl...@gmail.com>
> wrote:
> > Hi
> >
> > I just ran the osgi tests locally and stumbled across two issues
> >
> > 1)
> > Some weird maven duplicate test set issue about FtpConsumerTest. So I
> > disable that test to move on. I know the tests works fine when running
> > it manually, eg from an IDE etc. Anyway the globe keep on turning and
> > we can't be stuck fiddling with weird maven issues all day.
> >
> > 2)
> > The MailRouteTest no longer works. I guess its due those recent
> > changes in the Camel karaf feature.xml file. So I disabled the test.
> > The test relies on that there is a Mocked JavaMail provider installed,
> > that can act as the mail server. But it doesn't so it tries to connect
> > to a local running mail server on port 25.
> >
> > All the other tests passed.
> >
> > So lets close down this baby so we can cut a release for an overdue
> > release. We owe it to the community to bring out Camel 2.8.0 this
> > summer :)
> >
> > --
> > Claus Ibsen
> > -----------------
> > FuseSource
> > Email: cibsen@fusesource.com
> > Web: http://fusesource.com
> > Twitter: davsclaus, fusenews
> > Blog: http://davsclaus.blogspot.com/
> > Author of Camel in Action: http://www.manning.com/ibsen/
> >
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
So Camel 2.8.0 starts to look good.
The last CI test at Apache had only 1 unit test failure which is a non
deterministic test that can fail for some strange reason.
https://builds.apache.org/job/Camel.trunk.fulltest/366/
I also ran a local OSGi unit test this morning and they all passed.
In terms of ticket outstanding in JIRA then there is only 2 left
https://issues.apache.org/jira/browse/CAMEL-3774
https://issues.apache.org/jira/browse/CAMEL-4189
3774: This is about generating the manual when doing the release. I
guess Hadrian haven't had a look at it. Since we are able to cut the
release, I guess this ticket may be able to postpone for Camel 2.9
4189: This is about a config.properties in the karaf. As I understand
this config.properties file is not part of the release in the kit or
in the maven repository. Its used for the karaf validate plugin, to
validate the features.xml file. Correct me if I am wrong. This could
be post poned to Camel 2.9.
So from a JIRA point of view it seems good. Do anyone have any last
item tickets they would like addressed?
I have two tickets which we can discuss whether we want to delay the
release to get included
https://issues.apache.org/jira/browse/CAMEL-4212
https://issues.apache.org/jira/browse/CAMEL-4202
4212 is about supporting multi value headers in the HTTP related
components. This may be a bit more work, so we may consider scheduling
this for Camel 2.9. This is discussed on the @dev forum.
4202 is being discussed on the @user forum. Its about making
request/reply over JMS with fixed replyTo queues faster. It could be
worthwhile for the ppl who uses JMS to participate in the @user
discussion so we are able to agree upon some solution.
On Fri, Jul 8, 2011 at 10:53 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> I just ran the osgi tests locally and stumbled across two issues
>
> 1)
> Some weird maven duplicate test set issue about FtpConsumerTest. So I
> disable that test to move on. I know the tests works fine when running
> it manually, eg from an IDE etc. Anyway the globe keep on turning and
> we can't be stuck fiddling with weird maven issues all day.
>
> 2)
> The MailRouteTest no longer works. I guess its due those recent
> changes in the Camel karaf feature.xml file. So I disabled the test.
> The test relies on that there is a Mocked JavaMail provider installed,
> that can act as the mail server. But it doesn't so it tries to connect
> to a local running mail server on port 25.
>
> All the other tests passed.
>
> So lets close down this baby so we can cut a release for an overdue
> release. We owe it to the community to bring out Camel 2.8.0 this
> summer :)
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I just ran the osgi tests locally and stumbled across two issues
1)
Some weird maven duplicate test set issue about FtpConsumerTest. So I
disable that test to move on. I know the tests works fine when running
it manually, eg from an IDE etc. Anyway the globe keep on turning and
we can't be stuck fiddling with weird maven issues all day.
2)
The MailRouteTest no longer works. I guess its due those recent
changes in the Camel karaf feature.xml file. So I disabled the test.
The test relies on that there is a Mocked JavaMail provider installed,
that can act as the mail server. But it doesn't so it tries to connect
to a local running mail server on port 25.
All the other tests passed.
So lets close down this baby so we can cut a release for an overdue
release. We owe it to the community to bring out Camel 2.8.0 this
summer :)
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Willem:
> I don't want give the customer false assumption that we do regular patch
> release for the every major release of Camel from now on. I just want
> user to move on to the new major release of Camel and we can promise
> them we keep fixing the bugs in the trunk if they report it.
Why not? In what way false assumptions? Personally I would like to see
more patch releases out (3rd digit) and less minor ones (2nd digit). The
benefit and opportunity for the community is huge. There are a bunch of
other projects out there, many oss (like SwitchYard from RH that was
presented at CamelOne, ALv2 licensed too) that would benefit from
maintained branches. We shouldn't force them to upgrade.
Our user base is growing and we need to consider other projects too, not
only paying customers. If you want we can discuss general guidelines,
like how many versions back to support, release cycles etc. It would be
a great thing to commit as a community to a certain level of support.
Hadrian
On 07/06/2011 10:14 PM, Willem Jiang wrote:
> On 7/6/11 1:55 PM, Christian Schneider wrote:
>> Hi Willem,
>>
>> I can explain a bit from my experience as a user of Camel and CXF at my
>> former employer regarding patch releases.
>>
>> We updated our stack every 6 to 8 months. With CXF this mostly simply
>> worked. When some bug was detected we could create an issue and help fix
>> it. It went into the next patch release and we could
>> update to this one instead of the feature release.
>>
>> With Camel it was different. Every new release had a lot of new features
>> and changes. So we almost every time found a bug in the release that
>> prevented us to switch or that was a problem in production that needed
>> to be addressed. What went very well in Camel was reporting and fixing
>> bugs. I think Camel is probably the project I used where fixes to bugs
>> were made fastest. The problem was that the fix was only on trunk. Then
>> later it was incorporated into the new version. So my first strategy was
>> to update to the most current camel release when a bug was found and
>> fixed. The problem was that we almost every time found another problem
>> in the new release.
>> So what I did in the end was building our own release with the patches
>> to the bugs we had. This worked very well but not every customer wants
>> to do this.
>
> Camel is involved the very fast if you compare it with CXF.
> There could be more than 300 issues resolved in one major release of
> Camel. CXF is more stable after more than 5 years development, I can
> easily merge my patch for CXF trunk to 2.4.x and 2.3.x without changing
> anything. But if you merge the bug patch from Camel 2.8-SNAPSHOT to
> Camel 2.6.x, you may hit lots of conflicts.
>
> I don't want give the customer false assumption that we do regular patch
> release for the every major release of Camel from now on. I just want
> user to move on to the new major release of Camel and we can promise
> them we keep fixing the bugs in the trunk if they report it.
>>
>> Patch releases like 2.7.3 give the customer the fixes they need without
>> the breaking changes that cause new bugs. So from a customer standpoint
>> patch releases are very valueable. Of course they make life for us more
>> complicated so I think we should mostly only support one patch release
>> and one feature release at the same time.
>
> I agree we should do the the patch release for any security reason,
> because we take this responsibility without any condition.
>
>> Of course a company like Fuse
>> or Talend can also do patch releases on their own but I think it is
>> better to have these releases at apache so it is transparent to the
>> customer what is in each release and he has no fear of vendor lock in.
> Current we don't have any other rule for the patch release of 2.7.x,
> even 2.8.x. I bring this question out is I don't want to give the user a
> false promise that 2.7.x patch release has all the bug patches those we
> found in the new major release of 2.8.0 etc.
>
>>
>> Christian
>>
>>
>>
>>
>> Am 06.07.2011 04:09, schrieb Willem Jiang:
>>> Hi Hadrian,
>>>
>>> I think we are ready for the Camel 2.8.0 release.
>>> But I'm not sure why you are still planing to do the patch release for
>>> the 2.7.x as we never do this kind small patch release unless it
>>> relates to a serious security issue before.
>>>
>>> Can we just let the people move on to Camel 2.8.0 instead of confusing
>>> about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
>>>
>>> On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
>>>> Karaf 2.2.2 is now available and Willem did the upgrade. I think we can
>>>> get ready to start the release. Are there any other issues that must go
>>>> into 2.8.0?
>>>>
>>>> I would also build a 2.7.3 at the same time, there are a few fixes and
>>>> improvements, including some around xmlsecurity.
>>>>
>>>> Thoughts?
>>>> Hadrian
>>>>
>>>>
>>>> On 06/30/2011 11:07 PM, Willem Jiang wrote:
>>>>> Hi,
>>>>>
>>>>> I just applied the patch into trunk.
>>>>>
>>>>> On 7/1/11 12:36 AM, Donald Whytock wrote:
>>>>>> https://issues.apache.org/jira/browse/CAMEL-3948
>>>>>>
>>>>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com>
>>>>>> wrote:
>>>>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current
>>>>>>> trunk
>>>>>>> still needs my final patch.
>>>>>>>
>>>>>>> Don
>>>>>>>
>>>>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>>>>>> Onofré<jb...@nanthrax.net> wrote:
>>>>>>>> Hi Claus,
>>>>>>>>
>>>>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday.
>>>>>>>> Jamie
>>>>>>>> will cut off the release this afternoon.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2
>>>>>>>>> open
>>>>>>>>> tickets.
>>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>>>>>
>>>>>>>>> CAMEL-3774 is about generating the manual and is assigned to
>>>>>>>>> Hadrian.
>>>>>>>>>
>>>>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in
>>>>>>>>> progress.
>>>>>>>>> So by good chance we should be able to pickup that version when
>>>>>>>>> its
>>>>>>>>> released.
>>>>>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>>>>>>> (CAMEL-4144 is about some maven validate goal that would require
>>>>>>>>> Karaf
>>>>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>>>>>>>> absolutely fine)
>>>>>>>>>
>>>>>>>>> The CI servers also seems good. Although they tend to run out of
>>>>>>>>> memory at the end, such as when testing the examples. But those
>>>>>>>>> are
>>>>>>>>> the last piece of the build, and thus all components tests fine.
>>>>>>>>>
>>>>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on
>>>>>>>>> the CI
>>>>>>>>> servers and then start cutting the Camel 2.8 release. Would be
>>>>>>>>> good to
>>>>>>>>> get it out before the summer vacation starts. As well its more
>>>>>>>>> than 3
>>>>>>>>> months since Camel 2.7 was released.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus
>>>>>>>>> Ibsen<cl...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> Okay we should really start focusing on getting the last tickets
>>>>>>>>>> which
>>>>>>>>>> has been assigned for 2.8 release done now.
>>>>>>>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>>>>>>>> biggest release, since 2.0 went GA.
>>>>>>>>>>
>>>>>>>>>> So please take a look at your assigned tickets and get them
>>>>>>>>>> done, or
>>>>>>>>>> move them for 2.9.
>>>>>>>>>> Then keep eyes on CI servers and help fix any test failures,
>>>>>>>>>> so we
>>>>>>>>>> have green builds.
>>>>>>>>>>
>>>>>>>>>> The summer vacation period is approaching so we should IMHO get
>>>>>>>>>> the
>>>>>>>>>> 2.8 release out early next month if possible.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian
>>>>>>>>>> Zbarcea<hz...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I would propose starting to close down and prepare for the 2.8.0
>>>>>>>>>>> release
>>>>>>>>>>> in
>>>>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances
>>>>>>>>>>> are
>>>>>>>>>>> will
>>>>>>>>>>> be
>>>>>>>>>>> over 300 by the release time, probably setting a new record.
>>>>>>>>>>>
>>>>>>>>>>> As of now there are 17 issues unresolved, a few of them almost
>>>>>>>>>>> done, so
>>>>>>>>>>> by
>>>>>>>>>>> next week I assume there'll be significantly less. I would
>>>>>>>>>>> suggest
>>>>>>>>>>> shifting
>>>>>>>>>>> the focus from adding new features to stabilizing the build. If
>>>>>>>>>>> there
>>>>>>>>>>> are
>>>>>>>>>>> any issues you know of that you think absolutely must be in
>>>>>>>>>>> 2.8.0
>>>>>>>>>>> please
>>>>>>>>>>> shout and ask for help if needed (especially non committers
>>>>>>>>>>> subscribing
>>>>>>>>>>> to
>>>>>>>>>>> this list).
>>>>>>>>>>>
>>>>>>>>>>> Thoughts?
>>>>>>>>>>>
>>>>>>>>>>> Hadrian
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Claus Ibsen
>>>>>>>>>> -----------------
>>>>>>>>>> FuseSource
>>>>>>>>>> Email: cibsen@fusesource.com
>>>>>>>>>> Web: http://fusesource.com
>>>>>>>>>> Twitter: davsclaus, fusenews
>>>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Willem Jiang <wi...@gmail.com>.
On 7/6/11 1:55 PM, Christian Schneider wrote:
> Hi Willem,
>
> I can explain a bit from my experience as a user of Camel and CXF at my
> former employer regarding patch releases.
>
> We updated our stack every 6 to 8 months. With CXF this mostly simply
> worked. When some bug was detected we could create an issue and help fix
> it. It went into the next patch release and we could
> update to this one instead of the feature release.
>
> With Camel it was different. Every new release had a lot of new features
> and changes. So we almost every time found a bug in the release that
> prevented us to switch or that was a problem in production that needed
> to be addressed. What went very well in Camel was reporting and fixing
> bugs. I think Camel is probably the project I used where fixes to bugs
> were made fastest. The problem was that the fix was only on trunk. Then
> later it was incorporated into the new version. So my first strategy was
> to update to the most current camel release when a bug was found and
> fixed. The problem was that we almost every time found another problem
> in the new release.
> So what I did in the end was building our own release with the patches
> to the bugs we had. This worked very well but not every customer wants
> to do this.
Camel is involved the very fast if you compare it with CXF.
There could be more than 300 issues resolved in one major release of
Camel. CXF is more stable after more than 5 years development, I can
easily merge my patch for CXF trunk to 2.4.x and 2.3.x without changing
anything. But if you merge the bug patch from Camel 2.8-SNAPSHOT to
Camel 2.6.x, you may hit lots of conflicts.
I don't want give the customer false assumption that we do regular patch
release for the every major release of Camel from now on. I just want
user to move on to the new major release of Camel and we can promise
them we keep fixing the bugs in the trunk if they report it.
>
> Patch releases like 2.7.3 give the customer the fixes they need without
> the breaking changes that cause new bugs. So from a customer standpoint
> patch releases are very valueable. Of course they make life for us more
> complicated so I think we should mostly only support one patch release
> and one feature release at the same time.
I agree we should do the the patch release for any security reason,
because we take this responsibility without any condition.
>Of course a company like Fuse
> or Talend can also do patch releases on their own but I think it is
> better to have these releases at apache so it is transparent to the
> customer what is in each release and he has no fear of vendor lock in.
Current we don't have any other rule for the patch release of 2.7.x,
even 2.8.x. I bring this question out is I don't want to give the user a
false promise that 2.7.x patch release has all the bug patches those we
found in the new major release of 2.8.0 etc.
>
> Christian
>
>
>
>
> Am 06.07.2011 04:09, schrieb Willem Jiang:
>> Hi Hadrian,
>>
>> I think we are ready for the Camel 2.8.0 release.
>> But I'm not sure why you are still planing to do the patch release for
>> the 2.7.x as we never do this kind small patch release unless it
>> relates to a serious security issue before.
>>
>> Can we just let the people move on to Camel 2.8.0 instead of confusing
>> about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
>>
>> On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
>>> Karaf 2.2.2 is now available and Willem did the upgrade. I think we can
>>> get ready to start the release. Are there any other issues that must go
>>> into 2.8.0?
>>>
>>> I would also build a 2.7.3 at the same time, there are a few fixes and
>>> improvements, including some around xmlsecurity.
>>>
>>> Thoughts?
>>> Hadrian
>>>
>>>
>>> On 06/30/2011 11:07 PM, Willem Jiang wrote:
>>>> Hi,
>>>>
>>>> I just applied the patch into trunk.
>>>>
>>>> On 7/1/11 12:36 AM, Donald Whytock wrote:
>>>>> https://issues.apache.org/jira/browse/CAMEL-3948
>>>>>
>>>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com>
>>>>> wrote:
>>>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current
>>>>>> trunk
>>>>>> still needs my final patch.
>>>>>>
>>>>>> Don
>>>>>>
>>>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>>>>> Onofré<jb...@nanthrax.net> wrote:
>>>>>>> Hi Claus,
>>>>>>>
>>>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday.
>>>>>>> Jamie
>>>>>>> will cut off the release this afternoon.
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>>>>>>> tickets.
>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>>>>
>>>>>>>> CAMEL-3774 is about generating the manual and is assigned to
>>>>>>>> Hadrian.
>>>>>>>>
>>>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in
>>>>>>>> progress.
>>>>>>>> So by good chance we should be able to pickup that version when its
>>>>>>>> released.
>>>>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>>>>>> (CAMEL-4144 is about some maven validate goal that would require
>>>>>>>> Karaf
>>>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>>>>>>> absolutely fine)
>>>>>>>>
>>>>>>>> The CI servers also seems good. Although they tend to run out of
>>>>>>>> memory at the end, such as when testing the examples. But those are
>>>>>>>> the last piece of the build, and thus all components tests fine.
>>>>>>>>
>>>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on
>>>>>>>> the CI
>>>>>>>> servers and then start cutting the Camel 2.8 release. Would be
>>>>>>>> good to
>>>>>>>> get it out before the summer vacation starts. As well its more
>>>>>>>> than 3
>>>>>>>> months since Camel 2.7 was released.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> Okay we should really start focusing on getting the last tickets
>>>>>>>>> which
>>>>>>>>> has been assigned for 2.8 release done now.
>>>>>>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>>>>>>> biggest release, since 2.0 went GA.
>>>>>>>>>
>>>>>>>>> So please take a look at your assigned tickets and get them
>>>>>>>>> done, or
>>>>>>>>> move them for 2.9.
>>>>>>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>>>>>>> have green builds.
>>>>>>>>>
>>>>>>>>> The summer vacation period is approaching so we should IMHO get
>>>>>>>>> the
>>>>>>>>> 2.8 release out early next month if possible.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian
>>>>>>>>> Zbarcea<hz...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I would propose starting to close down and prepare for the 2.8.0
>>>>>>>>>> release
>>>>>>>>>> in
>>>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are
>>>>>>>>>> will
>>>>>>>>>> be
>>>>>>>>>> over 300 by the release time, probably setting a new record.
>>>>>>>>>>
>>>>>>>>>> As of now there are 17 issues unresolved, a few of them almost
>>>>>>>>>> done, so
>>>>>>>>>> by
>>>>>>>>>> next week I assume there'll be significantly less. I would
>>>>>>>>>> suggest
>>>>>>>>>> shifting
>>>>>>>>>> the focus from adding new features to stabilizing the build. If
>>>>>>>>>> there
>>>>>>>>>> are
>>>>>>>>>> any issues you know of that you think absolutely must be in 2.8.0
>>>>>>>>>> please
>>>>>>>>>> shout and ask for help if needed (especially non committers
>>>>>>>>>> subscribing
>>>>>>>>>> to
>>>>>>>>>> this list).
>>>>>>>>>>
>>>>>>>>>> Thoughts?
>>>>>>>>>>
>>>>>>>>>> Hadrian
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Claus Ibsen
>>>>>>>>> -----------------
>>>>>>>>> FuseSource
>>>>>>>>> Email: cibsen@fusesource.com
>>>>>>>>> Web: http://fusesource.com
>>>>>>>>> Twitter: davsclaus, fusenews
>>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Willem,
I can explain a bit from my experience as a user of Camel and CXF at my
former employer regarding patch releases.
We updated our stack every 6 to 8 months. With CXF this mostly simply
worked. When some bug was detected we could create an issue and help fix
it. It went into the next patch release and we could
update to this one instead of the feature release.
With Camel it was different. Every new release had a lot of new features
and changes. So we almost every time found a bug in the release that
prevented us to switch or that was a problem in production that needed
to be addressed. What went very well in Camel was reporting and fixing
bugs. I think Camel is probably the project I used where fixes to bugs
were made fastest. The problem was that the fix was only on trunk. Then
later it was incorporated into the new version. So my first strategy was
to update to the most current camel release when a bug was found and
fixed. The problem was that we almost every time found another problem
in the new release.
So what I did in the end was building our own release with the patches
to the bugs we had. This worked very well but not every customer wants
to do this.
Patch releases like 2.7.3 give the customer the fixes they need without
the breaking changes that cause new bugs. So from a customer standpoint
patch releases are very valueable. Of course they make life for us more
complicated so I think we should mostly only support one patch release
and one feature release at the same time. Of course a company like Fuse
or Talend can also do patch releases on their own but I think it is
better to have these releases at apache so it is transparent to the
customer what is in each release and he has no fear of vendor lock in.
Christian
Am 06.07.2011 04:09, schrieb Willem Jiang:
> Hi Hadrian,
>
> I think we are ready for the Camel 2.8.0 release.
> But I'm not sure why you are still planing to do the patch release for
> the 2.7.x as we never do this kind small patch release unless it
> relates to a serious security issue before.
>
> Can we just let the people move on to Camel 2.8.0 instead of confusing
> about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
>
> On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
>> Karaf 2.2.2 is now available and Willem did the upgrade. I think we can
>> get ready to start the release. Are there any other issues that must go
>> into 2.8.0?
>>
>> I would also build a 2.7.3 at the same time, there are a few fixes and
>> improvements, including some around xmlsecurity.
>>
>> Thoughts?
>> Hadrian
>>
>>
>> On 06/30/2011 11:07 PM, Willem Jiang wrote:
>>> Hi,
>>>
>>> I just applied the patch into trunk.
>>>
>>> On 7/1/11 12:36 AM, Donald Whytock wrote:
>>>> https://issues.apache.org/jira/browse/CAMEL-3948
>>>>
>>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com>
>>>> wrote:
>>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current
>>>>> trunk
>>>>> still needs my final patch.
>>>>>
>>>>> Don
>>>>>
>>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>>>> Onofré<jb...@nanthrax.net> wrote:
>>>>>> Hi Claus,
>>>>>>
>>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday.
>>>>>> Jamie
>>>>>> will cut off the release this afternoon.
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>>>>>> tickets.
>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>>>
>>>>>>> CAMEL-3774 is about generating the manual and is assigned to
>>>>>>> Hadrian.
>>>>>>>
>>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in
>>>>>>> progress.
>>>>>>> So by good chance we should be able to pickup that version when its
>>>>>>> released.
>>>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>>>>> (CAMEL-4144 is about some maven validate goal that would require
>>>>>>> Karaf
>>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>>>>>> absolutely fine)
>>>>>>>
>>>>>>> The CI servers also seems good. Although they tend to run out of
>>>>>>> memory at the end, such as when testing the examples. But those are
>>>>>>> the last piece of the build, and thus all components tests fine.
>>>>>>>
>>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on
>>>>>>> the CI
>>>>>>> servers and then start cutting the Camel 2.8 release. Would be
>>>>>>> good to
>>>>>>> get it out before the summer vacation starts. As well its more
>>>>>>> than 3
>>>>>>> months since Camel 2.7 was released.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Okay we should really start focusing on getting the last tickets
>>>>>>>> which
>>>>>>>> has been assigned for 2.8 release done now.
>>>>>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>>>>>> biggest release, since 2.0 went GA.
>>>>>>>>
>>>>>>>> So please take a look at your assigned tickets and get them
>>>>>>>> done, or
>>>>>>>> move them for 2.9.
>>>>>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>>>>>> have green builds.
>>>>>>>>
>>>>>>>> The summer vacation period is approaching so we should IMHO get
>>>>>>>> the
>>>>>>>> 2.8 release out early next month if possible.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian
>>>>>>>> Zbarcea<hz...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I would propose starting to close down and prepare for the 2.8.0
>>>>>>>>> release
>>>>>>>>> in
>>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are
>>>>>>>>> will
>>>>>>>>> be
>>>>>>>>> over 300 by the release time, probably setting a new record.
>>>>>>>>>
>>>>>>>>> As of now there are 17 issues unresolved, a few of them almost
>>>>>>>>> done, so
>>>>>>>>> by
>>>>>>>>> next week I assume there'll be significantly less. I would
>>>>>>>>> suggest
>>>>>>>>> shifting
>>>>>>>>> the focus from adding new features to stabilizing the build. If
>>>>>>>>> there
>>>>>>>>> are
>>>>>>>>> any issues you know of that you think absolutely must be in 2.8.0
>>>>>>>>> please
>>>>>>>>> shout and ask for help if needed (especially non committers
>>>>>>>>> subscribing
>>>>>>>>> to
>>>>>>>>> this list).
>>>>>>>>>
>>>>>>>>> Thoughts?
>>>>>>>>>
>>>>>>>>> Hadrian
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> FuseSource
>>>>>>>> Email: cibsen@fusesource.com
>>>>>>>> Web: http://fusesource.com
>>>>>>>> Twitter: davsclaus, fusenews
>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Willem Jiang <wi...@gmail.com>.
Hi Hadrian,
I think we are ready for the Camel 2.8.0 release.
But I'm not sure why you are still planing to do the patch release for
the 2.7.x as we never do this kind small patch release unless it relates
to a serious security issue before.
Can we just let the people move on to Camel 2.8.0 instead of confusing
about what's difference between the Camel 2.8.0 and Camel 2.7.3 ?
On 7/5/11 12:11 PM, Hadrian Zbarcea wrote:
> Karaf 2.2.2 is now available and Willem did the upgrade. I think we can
> get ready to start the release. Are there any other issues that must go
> into 2.8.0?
>
> I would also build a 2.7.3 at the same time, there are a few fixes and
> improvements, including some around xmlsecurity.
>
> Thoughts?
> Hadrian
>
>
> On 06/30/2011 11:07 PM, Willem Jiang wrote:
>> Hi,
>>
>> I just applied the patch into trunk.
>>
>> On 7/1/11 12:36 AM, Donald Whytock wrote:
>>> https://issues.apache.org/jira/browse/CAMEL-3948
>>>
>>> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com>
>>> wrote:
>>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current trunk
>>>> still needs my final patch.
>>>>
>>>> Don
>>>>
>>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>>> Onofré<jb...@nanthrax.net> wrote:
>>>>> Hi Claus,
>>>>>
>>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday.
>>>>> Jamie
>>>>> will cut off the release this afternoon.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>>>>> tickets.
>>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>>
>>>>>> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>>>>>>
>>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in
>>>>>> progress.
>>>>>> So by good chance we should be able to pickup that version when its
>>>>>> released.
>>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>>>> (CAMEL-4144 is about some maven validate goal that would require
>>>>>> Karaf
>>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>>>>> absolutely fine)
>>>>>>
>>>>>> The CI servers also seems good. Although they tend to run out of
>>>>>> memory at the end, such as when testing the examples. But those are
>>>>>> the last piece of the build, and thus all components tests fine.
>>>>>>
>>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on
>>>>>> the CI
>>>>>> servers and then start cutting the Camel 2.8 release. Would be
>>>>>> good to
>>>>>> get it out before the summer vacation starts. As well its more than 3
>>>>>> months since Camel 2.7 was released.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Okay we should really start focusing on getting the last tickets
>>>>>>> which
>>>>>>> has been assigned for 2.8 release done now.
>>>>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>>>>> biggest release, since 2.0 went GA.
>>>>>>>
>>>>>>> So please take a look at your assigned tickets and get them done, or
>>>>>>> move them for 2.9.
>>>>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>>>>> have green builds.
>>>>>>>
>>>>>>> The summer vacation period is approaching so we should IMHO get the
>>>>>>> 2.8 release out early next month if possible.
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I would propose starting to close down and prepare for the 2.8.0
>>>>>>>> release
>>>>>>>> in
>>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are
>>>>>>>> will
>>>>>>>> be
>>>>>>>> over 300 by the release time, probably setting a new record.
>>>>>>>>
>>>>>>>> As of now there are 17 issues unresolved, a few of them almost
>>>>>>>> done, so
>>>>>>>> by
>>>>>>>> next week I assume there'll be significantly less. I would suggest
>>>>>>>> shifting
>>>>>>>> the focus from adding new features to stabilizing the build. If
>>>>>>>> there
>>>>>>>> are
>>>>>>>> any issues you know of that you think absolutely must be in 2.8.0
>>>>>>>> please
>>>>>>>> shout and ask for help if needed (especially non committers
>>>>>>>> subscribing
>>>>>>>> to
>>>>>>>> this list).
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>> Hadrian
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> FuseSource
>>>>>>> Email: cibsen@fusesource.com
>>>>>>> Web: http://fusesource.com
>>>>>>> Twitter: davsclaus, fusenews
>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Karaf 2.2.2 is now available and Willem did the upgrade. I think we can
get ready to start the release. Are there any other issues that must go
into 2.8.0?
I would also build a 2.7.3 at the same time, there are a few fixes and
improvements, including some around xmlsecurity.
Thoughts?
Hadrian
On 06/30/2011 11:07 PM, Willem Jiang wrote:
> Hi,
>
> I just applied the patch into trunk.
>
> On 7/1/11 12:36 AM, Donald Whytock wrote:
>> https://issues.apache.org/jira/browse/CAMEL-3948
>>
>> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com>
>> wrote:
>>> Just a reminder...CAMEL-3948 is marked as fixed, but the current trunk
>>> still needs my final patch.
>>>
>>> Don
>>>
>>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste
>>> Onofré<jb...@nanthrax.net> wrote:
>>>> Hi Claus,
>>>>
>>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday.
>>>> Jamie
>>>> will cut off the release this afternoon.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>>>> tickets.
>>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>>
>>>>> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>>>>>
>>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in
>>>>> progress.
>>>>> So by good chance we should be able to pickup that version when its
>>>>> released.
>>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>>> (CAMEL-4144 is about some maven validate goal that would require Karaf
>>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>>>> absolutely fine)
>>>>>
>>>>> The CI servers also seems good. Although they tend to run out of
>>>>> memory at the end, such as when testing the examples. But those are
>>>>> the last piece of the build, and thus all components tests fine.
>>>>>
>>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
>>>>> servers and then start cutting the Camel 2.8 release. Would be good to
>>>>> get it out before the summer vacation starts. As well its more than 3
>>>>> months since Camel 2.7 was released.
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Okay we should really start focusing on getting the last tickets
>>>>>> which
>>>>>> has been assigned for 2.8 release done now.
>>>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>>>> biggest release, since 2.0 went GA.
>>>>>>
>>>>>> So please take a look at your assigned tickets and get them done, or
>>>>>> move them for 2.9.
>>>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>>>> have green builds.
>>>>>>
>>>>>> The summer vacation period is approaching so we should IMHO get the
>>>>>> 2.8 release out early next month if possible.
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I would propose starting to close down and prepare for the 2.8.0
>>>>>>> release
>>>>>>> in
>>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are
>>>>>>> will
>>>>>>> be
>>>>>>> over 300 by the release time, probably setting a new record.
>>>>>>>
>>>>>>> As of now there are 17 issues unresolved, a few of them almost
>>>>>>> done, so
>>>>>>> by
>>>>>>> next week I assume there'll be significantly less. I would suggest
>>>>>>> shifting
>>>>>>> the focus from adding new features to stabilizing the build. If
>>>>>>> there
>>>>>>> are
>>>>>>> any issues you know of that you think absolutely must be in 2.8.0
>>>>>>> please
>>>>>>> shout and ask for help if needed (especially non committers
>>>>>>> subscribing
>>>>>>> to
>>>>>>> this list).
>>>>>>>
>>>>>>> Thoughts?
>>>>>>>
>>>>>>> Hadrian
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> FuseSource
>>>>>> Email: cibsen@fusesource.com
>>>>>> Web: http://fusesource.com
>>>>>> Twitter: davsclaus, fusenews
>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Willem Jiang <wi...@gmail.com>.
Hi,
I just applied the patch into trunk.
On 7/1/11 12:36 AM, Donald Whytock wrote:
> https://issues.apache.org/jira/browse/CAMEL-3948
>
> On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock<dw...@gmail.com> wrote:
>> Just a reminder...CAMEL-3948 is marked as fixed, but the current trunk
>> still needs my final patch.
>>
>> Don
>>
>> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste Onofré<jb...@nanthrax.net> wrote:
>>> Hi Claus,
>>>
>>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday. Jamie
>>> will cut off the release this afternoon.
>>>
>>> Regards
>>> JB
>>>
>>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>>
>>>> Hi
>>>>
>>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>>> tickets.
>>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>>
>>>> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>>>>
>>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in progress.
>>>> So by good chance we should be able to pickup that version when its
>>>> released.
>>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>>> (CAMEL-4144 is about some maven validate goal that would require Karaf
>>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>>> absolutely fine)
>>>>
>>>> The CI servers also seems good. Although they tend to run out of
>>>> memory at the end, such as when testing the examples. But those are
>>>> the last piece of the build, and thus all components tests fine.
>>>>
>>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
>>>> servers and then start cutting the Camel 2.8 release. Would be good to
>>>> get it out before the summer vacation starts. As well its more than 3
>>>> months since Camel 2.7 was released.
>>>>
>>>>
>>>>
>>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>>>> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Okay we should really start focusing on getting the last tickets which
>>>>> has been assigned for 2.8 release done now.
>>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>>> biggest release, since 2.0 went GA.
>>>>>
>>>>> So please take a look at your assigned tickets and get them done, or
>>>>> move them for 2.9.
>>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>>> have green builds.
>>>>>
>>>>> The summer vacation period is approaching so we should IMHO get the
>>>>> 2.8 release out early next month if possible.
>>>>>
>>>>>
>>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I would propose starting to close down and prepare for the 2.8.0 release
>>>>>> in
>>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will
>>>>>> be
>>>>>> over 300 by the release time, probably setting a new record.
>>>>>>
>>>>>> As of now there are 17 issues unresolved, a few of them almost done, so
>>>>>> by
>>>>>> next week I assume there'll be significantly less. I would suggest
>>>>>> shifting
>>>>>> the focus from adding new features to stabilizing the build. If there
>>>>>> are
>>>>>> any issues you know of that you think absolutely must be in 2.8.0 please
>>>>>> shout and ask for help if needed (especially non committers subscribing
>>>>>> to
>>>>>> this list).
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> Hadrian
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> FuseSource
>>>>> Email: cibsen@fusesource.com
>>>>> Web: http://fusesource.com
>>>>> Twitter: davsclaus, fusenews
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Donald Whytock <dw...@gmail.com>.
https://issues.apache.org/jira/browse/CAMEL-3948
On Thu, Jun 30, 2011 at 12:35 PM, Donald Whytock <dw...@gmail.com> wrote:
> Just a reminder...CAMEL-3948 is marked as fixed, but the current trunk
> still needs my final patch.
>
> Don
>
> On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> Hi Claus,
>>
>> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday. Jamie
>> will cut off the release this afternoon.
>>
>> Regards
>> JB
>>
>> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>>
>>> Hi
>>>
>>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>>> tickets.
>>> - https://issues.apache.org/jira/browse/CAMEL-3774
>>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>>
>>> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>>>
>>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in progress.
>>> So by good chance we should be able to pickup that version when its
>>> released.
>>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>>> (CAMEL-4144 is about some maven validate goal that would require Karaf
>>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>>> absolutely fine)
>>>
>>> The CI servers also seems good. Although they tend to run out of
>>> memory at the end, such as when testing the examples. But those are
>>> the last piece of the build, and thus all components tests fine.
>>>
>>> I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
>>> servers and then start cutting the Camel 2.8 release. Would be good to
>>> get it out before the summer vacation starts. As well its more than 3
>>> months since Camel 2.7 was released.
>>>
>>>
>>>
>>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>>> wrote:
>>>>
>>>> Hi
>>>>
>>>> Okay we should really start focusing on getting the last tickets which
>>>> has been assigned for 2.8 release done now.
>>>> There is about 350 tickets on the roadmap, so its going to be the
>>>> biggest release, since 2.0 went GA.
>>>>
>>>> So please take a look at your assigned tickets and get them done, or
>>>> move them for 2.9.
>>>> Then keep eyes on CI servers and help fix any test failures, so we
>>>> have green builds.
>>>>
>>>> The summer vacation period is approaching so we should IMHO get the
>>>> 2.8 release out early next month if possible.
>>>>
>>>>
>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I would propose starting to close down and prepare for the 2.8.0 release
>>>>> in
>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will
>>>>> be
>>>>> over 300 by the release time, probably setting a new record.
>>>>>
>>>>> As of now there are 17 issues unresolved, a few of them almost done, so
>>>>> by
>>>>> next week I assume there'll be significantly less. I would suggest
>>>>> shifting
>>>>> the focus from adding new features to stabilizing the build. If there
>>>>> are
>>>>> any issues you know of that you think absolutely must be in 2.8.0 please
>>>>> shout and ask for help if needed (especially non committers subscribing
>>>>> to
>>>>> this list).
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Hadrian
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> FuseSource
>>>> Email: cibsen@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>
>>>
>>>
>>>
>>
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Donald Whytock <dw...@gmail.com>.
Just a reminder...CAMEL-3948 is marked as fixed, but the current trunk
still needs my final patch.
Don
On Thu, Jun 30, 2011 at 2:46 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi Claus,
>
> Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday. Jamie
> will cut off the release this afternoon.
>
> Regards
> JB
>
> On 06/30/2011 08:31 AM, Claus Ibsen wrote:
>>
>> Hi
>>
>> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open
>> tickets.
>> - https://issues.apache.org/jira/browse/CAMEL-3774
>> - https://issues.apache.org/jira/browse/CAMEL-4144
>>
>> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>>
>> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in progress.
>> So by good chance we should be able to pickup that version when its
>> released.
>> Alternatively we can stick to Karaf 2.2.1 which works fine.
>> (CAMEL-4144 is about some maven validate goal that would require Karaf
>> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
>> absolutely fine)
>>
>> The CI servers also seems good. Although they tend to run out of
>> memory at the end, such as when testing the examples. But those are
>> the last piece of the build, and thus all components tests fine.
>>
>> I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
>> servers and then start cutting the Camel 2.8 release. Would be good to
>> get it out before the summer vacation starts. As well its more than 3
>> months since Camel 2.7 was released.
>>
>>
>>
>> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com>
>> wrote:
>>>
>>> Hi
>>>
>>> Okay we should really start focusing on getting the last tickets which
>>> has been assigned for 2.8 release done now.
>>> There is about 350 tickets on the roadmap, so its going to be the
>>> biggest release, since 2.0 went GA.
>>>
>>> So please take a look at your assigned tickets and get them done, or
>>> move them for 2.9.
>>> Then keep eyes on CI servers and help fix any test failures, so we
>>> have green builds.
>>>
>>> The summer vacation period is approaching so we should IMHO get the
>>> 2.8 release out early next month if possible.
>>>
>>>
>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I would propose starting to close down and prepare for the 2.8.0 release
>>>> in
>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will
>>>> be
>>>> over 300 by the release time, probably setting a new record.
>>>>
>>>> As of now there are 17 issues unresolved, a few of them almost done, so
>>>> by
>>>> next week I assume there'll be significantly less. I would suggest
>>>> shifting
>>>> the focus from adding new features to stabilizing the build. If there
>>>> are
>>>> any issues you know of that you think absolutely must be in 2.8.0 please
>>>> shout and ask for help if needed (especially non committers subscribing
>>>> to
>>>> this list).
>>>>
>>>> Thoughts?
>>>>
>>>> Hadrian
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>
>>
>>
>>
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Claus,
Regarding Karaf 2.2.2, I've released OPS4J dependencies yesterday. Jamie
will cut off the release this afternoon.
Regards
JB
On 06/30/2011 08:31 AM, Claus Ibsen wrote:
> Hi
>
> Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open tickets.
> - https://issues.apache.org/jira/browse/CAMEL-3774
> - https://issues.apache.org/jira/browse/CAMEL-4144
>
> CAMEL-3774 is about generating the manual and is assigned to Hadrian.
>
> CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in progress.
> So by good chance we should be able to pickup that version when its released.
> Alternatively we can stick to Karaf 2.2.1 which works fine.
> (CAMEL-4144 is about some maven validate goal that would require Karaf
> 2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
> absolutely fine)
>
> The CI servers also seems good. Although they tend to run out of
> memory at the end, such as when testing the examples. But those are
> the last piece of the build, and thus all components tests fine.
>
> I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
> servers and then start cutting the Camel 2.8 release. Would be good to
> get it out before the summer vacation starts. As well its more than 3
> months since Camel 2.7 was released.
>
>
>
> On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen<cl...@gmail.com> wrote:
>> Hi
>>
>> Okay we should really start focusing on getting the last tickets which
>> has been assigned for 2.8 release done now.
>> There is about 350 tickets on the roadmap, so its going to be the
>> biggest release, since 2.0 went GA.
>>
>> So please take a look at your assigned tickets and get them done, or
>> move them for 2.9.
>> Then keep eyes on CI servers and help fix any test failures, so we
>> have green builds.
>>
>> The summer vacation period is approaching so we should IMHO get the
>> 2.8 release out early next month if possible.
>>
>>
>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com> wrote:
>>> Hi,
>>>
>>> I would propose starting to close down and prepare for the 2.8.0 release in
>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
>>> over 300 by the release time, probably setting a new record.
>>>
>>> As of now there are 17 issues unresolved, a few of them almost done, so by
>>> next week I assume there'll be significantly less. I would suggest shifting
>>> the focus from adding new features to stabilizing the build. If there are
>>> any issues you know of that you think absolutely must be in 2.8.0 please
>>> shout and ask for help if needed (especially non committers subscribing to
>>> this list).
>>>
>>> Thoughts?
>>>
>>> Hadrian
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>
>
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Okay the JIRA roadmap for Camel 2.8 seems good now. There is 2 open tickets.
- https://issues.apache.org/jira/browse/CAMEL-3774
- https://issues.apache.org/jira/browse/CAMEL-4144
CAMEL-3774 is about generating the manual and is assigned to Hadrian.
CAMEL-4144 is about upgrading to Karaf 2.2.2. That release is in progress.
So by good chance we should be able to pickup that version when its released.
Alternatively we can stick to Karaf 2.2.1 which works fine.
(CAMEL-4144 is about some maven validate goal that would require Karaf
2.2.2 to pickup a fix in Karaf, but running Camel in Karaf is
absolutely fine)
The CI servers also seems good. Although they tend to run out of
memory at the end, such as when testing the examples. But those are
the last piece of the build, and thus all components tests fine.
I suggest that when Karaf 2.2.2 is out we git it a few spins on the CI
servers and then start cutting the Camel 2.8 release. Would be good to
get it out before the summer vacation starts. As well its more than 3
months since Camel 2.7 was released.
On Mon, Jun 27, 2011 at 9:35 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Okay we should really start focusing on getting the last tickets which
> has been assigned for 2.8 release done now.
> There is about 350 tickets on the roadmap, so its going to be the
> biggest release, since 2.0 went GA.
>
> So please take a look at your assigned tickets and get them done, or
> move them for 2.9.
> Then keep eyes on CI servers and help fix any test failures, so we
> have green builds.
>
> The summer vacation period is approaching so we should IMHO get the
> 2.8 release out early next month if possible.
>
>
> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
>> Hi,
>>
>> I would propose starting to close down and prepare for the 2.8.0 release in
>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
>> over 300 by the release time, probably setting a new record.
>>
>> As of now there are 17 issues unresolved, a few of them almost done, so by
>> next week I assume there'll be significantly less. I would suggest shifting
>> the focus from adding new features to stabilizing the build. If there are
>> any issues you know of that you think absolutely must be in 2.8.0 please
>> shout and ask for help if needed (especially non committers subscribing to
>> this list).
>>
>> Thoughts?
>>
>> Hadrian
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Okay we should really start focusing on getting the last tickets which
has been assigned for 2.8 release done now.
There is about 350 tickets on the roadmap, so its going to be the
biggest release, since 2.0 went GA.
So please take a look at your assigned tickets and get them done, or
move them for 2.9.
Then keep eyes on CI servers and help fix any test failures, so we
have green builds.
The summer vacation period is approaching so we should IMHO get the
2.8 release out early next month if possible.
On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> Hi,
>
> I would propose starting to close down and prepare for the 2.8.0 release in
> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
> over 300 by the release time, probably setting a new record.
>
> As of now there are 17 issues unresolved, a few of them almost done, so by
> next week I assume there'll be significantly less. I would suggest shifting
> the focus from adding new features to stabilizing the build. If there are
> any issues you know of that you think absolutely must be in 2.8.0 please
> shout and ask for help if needed (especially non committers subscribing to
> this list).
>
> Thoughts?
>
> Hadrian
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Daniel Kulp <dk...@apache.org>.
> >
> > And I wonder if there is any CXF 2.4.1 coming out soon?
>
> CXF 2.4.1 will be release in a week.
Or less. I'm doing the builds today. :-)
Dan
On Thursday, June 09, 2011 9:17:53 AM Willem Jiang wrote:
> On 6/9/11 9:01 PM, Claus Ibsen wrote:
> > On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
wrote:
> >> Hi,
> >>
> >> I would propose starting to close down and prepare for the 2.8.0 release
> >> in 2-3 weeks. There are already 282 issues for 2.8.0 and chances are
> >> will be over 300 by the release time, probably setting a new record.
> >>
> >> As of now there are 17 issues unresolved, a few of them almost done, so
> >> by next week I assume there'll be significantly less. I would suggest
> >> shifting the focus from adding new features to stabilizing the build.
> >> If there are any issues you know of that you think absolutely must be
> >> in 2.8.0 please shout and ask for help if needed (especially non
> >> committers subscribing to this list).
> >>
> >> Thoughts?
> >
> > A good idea. I will get that error handler stuff sorted as well. I am
> > almost got my hands free for getting back to that today.
> >
> > At CamelOne I spoke to Johan, and he said he will finish the last
> > pieces of the OSGI blueprint XML namespace stuff for camel-cxf. But so
> > far he havent done that yet. It would of course be nice to get those
> > into the 2.8 release.
> >
> > We are also dependent on Karaf 2.2.2 being released first. So we
> > should ask them about an ETA and consider doing a release sooner this
> > month.
> >
> > And I wonder if there is any CXF 2.4.1 coming out soon?
>
> CXF 2.4.1 will be release in a week.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Willem Jiang <wi...@gmail.com>.
On 6/9/11 9:01 PM, Claus Ibsen wrote:
> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com> wrote:
>> Hi,
>>
>> I would propose starting to close down and prepare for the 2.8.0 release in
>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
>> over 300 by the release time, probably setting a new record.
>>
>> As of now there are 17 issues unresolved, a few of them almost done, so by
>> next week I assume there'll be significantly less. I would suggest shifting
>> the focus from adding new features to stabilizing the build. If there are
>> any issues you know of that you think absolutely must be in 2.8.0 please
>> shout and ask for help if needed (especially non committers subscribing to
>> this list).
>>
>> Thoughts?
>>
>
> A good idea. I will get that error handler stuff sorted as well. I am
> almost got my hands free for getting back to that today.
>
> At CamelOne I spoke to Johan, and he said he will finish the last
> pieces of the OSGI blueprint XML namespace stuff for camel-cxf. But so
> far he havent done that yet. It would of course be nice to get those
> into the 2.8 release.
>
> We are also dependent on Karaf 2.2.2 being released first. So we
> should ask them about an ETA and consider doing a release sooner this
> month.
>
> And I wonder if there is any CXF 2.4.1 coming out soon?
>
>
CXF 2.4.1 will be release in a week.
>
>
>> Hadrian
>>
>
>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> Hi,
>
> I would propose starting to close down and prepare for the 2.8.0 release in
> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
> over 300 by the release time, probably setting a new record.
>
> As of now there are 17 issues unresolved, a few of them almost done, so by
> next week I assume there'll be significantly less. I would suggest shifting
> the focus from adding new features to stabilizing the build. If there are
> any issues you know of that you think absolutely must be in 2.8.0 please
> shout and ask for help if needed (especially non committers subscribing to
> this list).
>
> Thoughts?
>
A good idea. I will get that error handler stuff sorted as well. I am
almost got my hands free for getting back to that today.
At CamelOne I spoke to Johan, and he said he will finish the last
pieces of the OSGI blueprint XML namespace stuff for camel-cxf. But so
far he havent done that yet. It would of course be nice to get those
into the 2.8 release.
We are also dependent on Karaf 2.2.2 being released first. So we
should ask them about an ETA and consider doing a release sooner this
month.
And I wonder if there is any CXF 2.4.1 coming out soon?
> Hadrian
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Donald Whytock <dw...@gmail.com>.
Done. Thanks.
On Sat, Jun 18, 2011 at 4:04 AM, Claus Ibsen <cl...@gmail.com> wrote:
> On Sat, Jun 18, 2011 at 1:08 AM, Donald Whytock <dw...@gmail.com> wrote:
>> I've got a patch to contribute for camel-mail. Is there still time to
>> get that in?
>>
>
> Yeah try to get the patch by start of next week at the latest.
>
>> Don
>>
>> On Thu, Jun 16, 2011 at 2:48 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>> Hi Claus,
>>>
>>> +1 to release Camel 2.8.0. I'm working on ServiceMix components using Camel
>>> 2.8-SNAPSHOT, so I'm quite ready to integrate Camel 2.8.0 in ServiceMix :)
>>>
>>> Thanks,
>>> Regards
>>> JB
>>>
>>> On 06/16/2011 07:44 AM, Claus Ibsen wrote:
>>>>
>>>> Hi
>>>>
>>>> Could you take a look at the assigned tickets you have which is
>>>> targeted for Camel 2.8.0 and get those resolved in due time.
>>>>
>>>> In terms of the CXF blueprint namespace handler, I have created
>>>> sub-tickets for the remaning work which can be postponed to Camel 2.9.
>>>> So we only need to add a bit of documentation of this new feature.
>>>>
>>>> CXF 2.4.1 has been updated so we are good there.
>>>>
>>>> In terms of Karaf, we should be able to run on Karaf 2.2.1. Our osgi
>>>> tests runs on that version.
>>>>
>>>> So lets try to get the last tickets resolved, so we are in shape for
>>>> cutting a release later this month. Would be good to get this big
>>>> Camel 2.8 release out before the summer vacation start to hit us.
>>>>
>>>> Hadrian what does your time schedule look like? Do you have time to
>>>> cut a release, if possible (fingers crossed), sometime next week. Or
>>>> the week thereafter?
>>>>
>>>>
>>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I would propose starting to close down and prepare for the 2.8.0 release
>>>>> in
>>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
>>>>> over 300 by the release time, probably setting a new record.
>>>>>
>>>>> As of now there are 17 issues unresolved, a few of them almost done, so
>>>>> by
>>>>> next week I assume there'll be significantly less. I would suggest
>>>>> shifting
>>>>> the focus from adding new features to stabilizing the build. If there are
>>>>> any issues you know of that you think absolutely must be in 2.8.0 please
>>>>> shout and ask for help if needed (especially non committers subscribing
>>>>> to
>>>>> this list).
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Hadrian
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Sat, Jun 18, 2011 at 1:08 AM, Donald Whytock <dw...@gmail.com> wrote:
> I've got a patch to contribute for camel-mail. Is there still time to
> get that in?
>
Yeah try to get the patch by start of next week at the latest.
> Don
>
> On Thu, Jun 16, 2011 at 2:48 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> Hi Claus,
>>
>> +1 to release Camel 2.8.0. I'm working on ServiceMix components using Camel
>> 2.8-SNAPSHOT, so I'm quite ready to integrate Camel 2.8.0 in ServiceMix :)
>>
>> Thanks,
>> Regards
>> JB
>>
>> On 06/16/2011 07:44 AM, Claus Ibsen wrote:
>>>
>>> Hi
>>>
>>> Could you take a look at the assigned tickets you have which is
>>> targeted for Camel 2.8.0 and get those resolved in due time.
>>>
>>> In terms of the CXF blueprint namespace handler, I have created
>>> sub-tickets for the remaning work which can be postponed to Camel 2.9.
>>> So we only need to add a bit of documentation of this new feature.
>>>
>>> CXF 2.4.1 has been updated so we are good there.
>>>
>>> In terms of Karaf, we should be able to run on Karaf 2.2.1. Our osgi
>>> tests runs on that version.
>>>
>>> So lets try to get the last tickets resolved, so we are in shape for
>>> cutting a release later this month. Would be good to get this big
>>> Camel 2.8 release out before the summer vacation start to hit us.
>>>
>>> Hadrian what does your time schedule look like? Do you have time to
>>> cut a release, if possible (fingers crossed), sometime next week. Or
>>> the week thereafter?
>>>
>>>
>>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I would propose starting to close down and prepare for the 2.8.0 release
>>>> in
>>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
>>>> over 300 by the release time, probably setting a new record.
>>>>
>>>> As of now there are 17 issues unresolved, a few of them almost done, so
>>>> by
>>>> next week I assume there'll be significantly less. I would suggest
>>>> shifting
>>>> the focus from adding new features to stabilizing the build. If there are
>>>> any issues you know of that you think absolutely must be in 2.8.0 please
>>>> shout and ask for help if needed (especially non committers subscribing
>>>> to
>>>> this list).
>>>>
>>>> Thoughts?
>>>>
>>>> Hadrian
>>>>
>>>
>>>
>>>
>>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Donald Whytock <dw...@gmail.com>.
I've got a patch to contribute for camel-mail. Is there still time to
get that in?
Don
On Thu, Jun 16, 2011 at 2:48 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi Claus,
>
> +1 to release Camel 2.8.0. I'm working on ServiceMix components using Camel
> 2.8-SNAPSHOT, so I'm quite ready to integrate Camel 2.8.0 in ServiceMix :)
>
> Thanks,
> Regards
> JB
>
> On 06/16/2011 07:44 AM, Claus Ibsen wrote:
>>
>> Hi
>>
>> Could you take a look at the assigned tickets you have which is
>> targeted for Camel 2.8.0 and get those resolved in due time.
>>
>> In terms of the CXF blueprint namespace handler, I have created
>> sub-tickets for the remaning work which can be postponed to Camel 2.9.
>> So we only need to add a bit of documentation of this new feature.
>>
>> CXF 2.4.1 has been updated so we are good there.
>>
>> In terms of Karaf, we should be able to run on Karaf 2.2.1. Our osgi
>> tests runs on that version.
>>
>> So lets try to get the last tickets resolved, so we are in shape for
>> cutting a release later this month. Would be good to get this big
>> Camel 2.8 release out before the summer vacation start to hit us.
>>
>> Hadrian what does your time schedule look like? Do you have time to
>> cut a release, if possible (fingers crossed), sometime next week. Or
>> the week thereafter?
>>
>>
>> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> I would propose starting to close down and prepare for the 2.8.0 release
>>> in
>>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
>>> over 300 by the release time, probably setting a new record.
>>>
>>> As of now there are 17 issues unresolved, a few of them almost done, so
>>> by
>>> next week I assume there'll be significantly less. I would suggest
>>> shifting
>>> the focus from adding new features to stabilizing the build. If there are
>>> any issues you know of that you think absolutely must be in 2.8.0 please
>>> shout and ask for help if needed (especially non committers subscribing
>>> to
>>> this list).
>>>
>>> Thoughts?
>>>
>>> Hadrian
>>>
>>
>>
>>
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Claus,
+1 to release Camel 2.8.0. I'm working on ServiceMix components using
Camel 2.8-SNAPSHOT, so I'm quite ready to integrate Camel 2.8.0 in
ServiceMix :)
Thanks,
Regards
JB
On 06/16/2011 07:44 AM, Claus Ibsen wrote:
> Hi
>
> Could you take a look at the assigned tickets you have which is
> targeted for Camel 2.8.0 and get those resolved in due time.
>
> In terms of the CXF blueprint namespace handler, I have created
> sub-tickets for the remaning work which can be postponed to Camel 2.9.
> So we only need to add a bit of documentation of this new feature.
>
> CXF 2.4.1 has been updated so we are good there.
>
> In terms of Karaf, we should be able to run on Karaf 2.2.1. Our osgi
> tests runs on that version.
>
> So lets try to get the last tickets resolved, so we are in shape for
> cutting a release later this month. Would be good to get this big
> Camel 2.8 release out before the summer vacation start to hit us.
>
> Hadrian what does your time schedule look like? Do you have time to
> cut a release, if possible (fingers crossed), sometime next week. Or
> the week thereafter?
>
>
> On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea<hz...@gmail.com> wrote:
>> Hi,
>>
>> I would propose starting to close down and prepare for the 2.8.0 release in
>> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
>> over 300 by the release time, probably setting a new record.
>>
>> As of now there are 17 issues unresolved, a few of them almost done, so by
>> next week I assume there'll be significantly less. I would suggest shifting
>> the focus from adding new features to stabilizing the build. If there are
>> any issues you know of that you think absolutely must be in 2.8.0 please
>> shout and ask for help if needed (especially non committers subscribing to
>> this list).
>>
>> Thoughts?
>>
>> Hadrian
>>
>
>
>
Re: [DISCUSS] Closing down for the 2.8.0 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Could you take a look at the assigned tickets you have which is
targeted for Camel 2.8.0 and get those resolved in due time.
In terms of the CXF blueprint namespace handler, I have created
sub-tickets for the remaning work which can be postponed to Camel 2.9.
So we only need to add a bit of documentation of this new feature.
CXF 2.4.1 has been updated so we are good there.
In terms of Karaf, we should be able to run on Karaf 2.2.1. Our osgi
tests runs on that version.
So lets try to get the last tickets resolved, so we are in shape for
cutting a release later this month. Would be good to get this big
Camel 2.8 release out before the summer vacation start to hit us.
Hadrian what does your time schedule look like? Do you have time to
cut a release, if possible (fingers crossed), sometime next week. Or
the week thereafter?
On Thu, Jun 9, 2011 at 2:47 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> Hi,
>
> I would propose starting to close down and prepare for the 2.8.0 release in
> 2-3 weeks. There are already 282 issues for 2.8.0 and chances are will be
> over 300 by the release time, probably setting a new record.
>
> As of now there are 17 issues unresolved, a few of them almost done, so by
> next week I assume there'll be significantly less. I would suggest shifting
> the focus from adding new features to stabilizing the build. If there are
> any issues you know of that you think absolutely must be in 2.8.0 please
> shout and ask for help if needed (especially non committers subscribing to
> this list).
>
> Thoughts?
>
> Hadrian
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/