There were some questions about why we are doing 1.5.0.1 instead of 1.5.1. The last time we did a 1.x.y release, it was a “real” maintenance release with real bug fixes and it was recommended that the users upgrade to that release (1.3.1 release). This time, there is no real difference from a user perspective for 1.5.0 and 1.5.0.1 except being compatible with a newer HBase release and the ability for BigTop to ship it. For all practical purposes, this is the same release as Flume 1.5.0 - which is why I chose to call it 1.5.0.1 rather than 1.5.1.
Thanks, Hari On Tuesday, June 10, 2014 at 8:50 PM, Jarek Jarcec Cecho wrote: > +1. > > Looks good to me. > > Jarcec > > On Tue, Jun 10, 2014 at 03:40:25PM -0700, Hari Shreedharan wrote: > > This is a vote for the next release of Apache Flume, version 1.5.0.1. We > > are voting on release candidate RC1. > > > > It fixes the following issues: > > http://s.apache.org/v7X > > > > *** Please cast your vote within the next 72 hours *** > > > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1) > > for the source and binary artifacts can be found here: > > https://people.apache.org/~hshreedharan/apache-flume-1.5.0.1-rc1/ > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapacheflume-1004/ > > > > The tag to be voted on: > > > > https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=ceda6aa1126a01370641caf729d8b1dd6d80aa61 > > > > Flume's KEYS file containing PGP keys we use to sign the release: > > http://www.apache.org/dist/flume/KEYS > > > > > > Thanks, > > Hari > > > > >
