Yes, I guess this makes sense. Should we also build a new patch release for the 2.15.x branch in order to this security fix out?
On Mon, Nov 16, 2015 at 5:52 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > I wonder if we should cancel this vote, and redo the release because > since there has been a commit on master and the 2.16 and 2.15 branches > that upgrades the > commons-collection to a version that has a security issue fix. > > https://blogs.apache.org/foundation/entry/apache_commons_statement_to_widespread > > > On Mon, Nov 16, 2015 at 11:05 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> +1 >> >> I tested with the camel in action source code and it was fine. >> >> On Sat, Nov 14, 2015 at 8:35 AM, Gregor Zurowski >> <gre...@list.zurowski.org> wrote: >>> Hi Everyone: >>> >>> This is a vote to release Apache Camel 2.16.1 that has over 60 fixes >>> and improvements. >>> >>> Release notes: >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12333749 >>> >>> Staging repository: >>> https://repository.apache.org/content/repositories/orgapachecamel-1042/ >>> >>> Tarballs: >>> https://repository.apache.org/content/repositories/orgapachecamel-1042/org/apache/camel/apache-camel/2.16.1/ >>> >>> Tag: >>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ce71d873fed79c72c48da951117a1544613d1626 >>> >>> Please test this release candidate and cast your vote. >>> [ ] +1 Release the binary as Apache Camel 2.16.1 >>> [ ] -1 Veto the release (provide specific comments) >>> >>> The vote is open for at least 72 hours. >>> >>> Thanks, >>> Gregor >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
