You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Magnus Heino <ma...@filur.org> on 2008/02/27 09:08:30 UTC
Camel needs milestones
> been fixed since 1.2.0 (we so need 1.3.0 to be released! :)
>
Wouldn't it be possible to have milestone-releases?
Right now we are using 1.2.0, and many of the problems we have are fixed in
1.3.0-SNAPSHOT. But if I change the maven build to use the snapshot, it will
check for new versions every now and then, and that is something I don't
want. I don't want to spend hours debugging my app just because todays
snapshot-build of camel might be broken.
Using a fixed milestone-release of 1.3 on the other hand, would be no
problem.
So go change 1.3.0-SNAPSHOT to 1.3.0-m1, mvn deploy, and change back to
1.3.0-SNAPSHOT and continue woking on all the great stuff! :-)
--
/Magnus Heino
Re: Camel needs milestones
Posted by James Strachan <ja...@gmail.com>.
On 27/02/2008, Magnus Heino <ma...@filur.org> wrote:
> >
> > I'm hoping we can get 1.3.0 out ASAP - in the next couple of days
> > hopefully; its pretty much ready to go...
> >
>
>
> Ok, I was looking at
> https://issues.apache.org/activemq/browse/CAMEL?report=com.atlassian.jira.plugin.system.project:roadmap-panelthat
> lists 33 issues that should be resolved before
> 1.3.
We tend to mark most issues we're gonna solve soon as being in the
next release; then when we cut a release they move to the next one
(1.4) those that we don't get to.
> Looking forward to the new release then :)
Me too! :)
If anyone wants any particular patches/fixes in 1.3.0 now is a good
time to speak up; hopefully once we've got the build looking good we
can cut another RC and see how we go from there.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
Re: Camel needs milestones
Posted by Magnus Heino <ma...@filur.org>.
>
> I'm hoping we can get 1.3.0 out ASAP - in the next couple of days
> hopefully; its pretty much ready to go...
>
Ok, I was looking at
https://issues.apache.org/activemq/browse/CAMEL?report=com.atlassian.jira.plugin.system.project:roadmap-panelthat
lists 33 issues that should be resolved before
1.3.
Looking forward to the new release then :)
--
/Magnus Heino
Re: Camel needs milestones
Posted by James Strachan <ja...@gmail.com>.
On 27/02/2008, Magnus Heino <ma...@filur.org> wrote:
> > been fixed since 1.2.0 (we so need 1.3.0 to be released! :)
> >
>
> Wouldn't it be possible to have milestone-releases?
>
> Right now we are using 1.2.0, and many of the problems we have are fixed in
> 1.3.0-SNAPSHOT. But if I change the maven build to use the snapshot, it will
> check for new versions every now and then, and that is something I don't
> want. I don't want to spend hours debugging my app just because todays
> snapshot-build of camel might be broken.
>
> Using a fixed milestone-release of 1.3 on the other hand, would be no
> problem.
>
> So go change 1.3.0-SNAPSHOT to 1.3.0-m1, mvn deploy, and change back to
> 1.3.0-SNAPSHOT and continue woking on all the great stuff! :-)
I'm hoping we can get 1.3.0 out ASAP - in the next couple of days
hopefully; its pretty much ready to go...
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
Re: Camel needs milestones
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Yeah,
I am working on exactly that. The last issue I am trying to solve is
the bad spring.schema and handler generated in the kit reported
against RC1 (see CAMEL-301). That fix (as mentioned in the comments)
breaks the osgi bundles. I fixed a good chunk of it last night with
help from Chris Custine from SMX.
Keep your fingers crossed,
Hadrian
On Feb 27, 2008, at 3:08 AM, Magnus Heino wrote:
>> been fixed since 1.2.0 (we so need 1.3.0 to be released! :)
>>
>
> Wouldn't it be possible to have milestone-releases?
>
> Right now we are using 1.2.0, and many of the problems we have are
> fixed in
> 1.3.0-SNAPSHOT. But if I change the maven build to use the snapshot,
> it will
> check for new versions every now and then, and that is something I
> don't
> want. I don't want to spend hours debugging my app just because todays
> snapshot-build of camel might be broken.
>
> Using a fixed milestone-release of 1.3 on the other hand, would be no
> problem.
>
> So go change 1.3.0-SNAPSHOT to 1.3.0-m1, mvn deploy, and change back
> to
> 1.3.0-SNAPSHOT and continue woking on all the great stuff! :-)
>
> --
>
> /Magnus Heino