Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.219.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALhQg-Y0BaMGxqRFgabm3sT-K-j8hb5TydKYLaOdAr4wZ0RPPg@mail.gmail.com>
References: 
 <CALhQg-Y0BaMGxqRFgabm3sT-K-j8hb5TydKYLaOdAr4wZ0RPPg@mail.gmail.com>
Date: Sun, 27 Jan 2013 14:35:35 +0100
Message-ID: 
 <CALvzYd8SFQ-zMfscJeH0ZKS+nzhcdgBfa==ysa7LnS-jCW9EJQ@mail.gmail.com>
Subject: Re: [camel-extra] 2.10.1 release
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: dev@camel.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff1ce463f6e3f04d4453cb6

--e89a8ff1ce463f6e3f04d4453cb6
Content-Type: text/plain; charset=ISO-8859-1

It looks good for me.

For Spring we have a broad version range:
org.springframework.transaction;version="[3.0,4)" for camel-extra-2.10.x
and [3.1,4) on trunk.

In Apache Camel we set it to [3.0,3.3) for Camel 2.11. We should use the
same version range here.

But go ahead with the camel-extra-2.10.1 release and fix it in
camel-extra-2.10.2.

Best,
Christian


On Wed, Jan 23, 2013 at 1:35 PM, Henryk Konsek <hekonsek@gmail.com> wrote:

> Hi,
>
> I've just created maintenance branch for Camel Extra 2.10.x. I've also
> merged OSGI imports fix [2] from trunk into it.
>
> I'd like to start process of releasing Camel Extra 2.10.1.
>
> Anybody wants to object?
>
> Best regards.
>
> [1]
> http://code.google.com/a/apache-extras.org/p/camel-extra/source/browse/#svn%2Fbranches%2Fcamel-extra-2.10.x
> [2]
> http://code.google.com/a/apache-extras.org/p/camel-extra/issues/detail?id=30
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>


--

--e89a8ff1ce463f6e3f04d4453cb6--