Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
In-Reply-To: <CAGB5yNmvXYCJcJD25dHtdH59hDoF__+Xp+uXO++-yj-_Ge6+3Q@mail.gmail.com>
References: <CAGB5yNmvXYCJcJD25dHtdH59hDoF__+Xp+uXO++-yj-_Ge6+3Q@mail.gmail.com>
From: Gregor Zurowski <gregor@list.zurowski.org>
Date: Thu, 14 Sep 2017 20:52:44 +0200
Message-ID: <CADL1oAq=T-zgSPZzGgrtM0pCq6-54EX+4YhuP5uQhOt=sZwGNQ@mail.gmail.com>
Subject: Re: [DISCUSS] - Doing last Camel 2.18.5 release before 2.20.0 release
To: dev@camel.apache.org
Content-Type: text/plain; charset="UTF-8"
archived-at: Thu, 14 Sep 2017 18:53:32 -0000

+1 for cutting the last 2.18.x release.  I can take care of this over
the upcoming weekend.

Gregor

On Thu, Sep 14, 2017 at 7:56 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
> Hi
>
> As we plan to release Apache Camel 2.20.0 at the end of this month
> (there is another thread on @dev about this) then we should talk about
> doing the last 2.18.x release which will be 2.18.5.
>
> Maybe we can release 2.18.5 ahead of time before 2.20.0. A new big
> minor release like 2.20.0 tend to have more eye's catching things here
> and there, and over the many years we have had to cut multiple RC's
> before a new minor release was approved.
>
> So in light of this maybe, we can us the "quiet" time until we start
> cutting the 2.20.0 RC candidates to get 2.18.5 release and out of our
> hands.
>
> Any thoughts?
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2