Roshan, 

No. The released artifacts are going to be on hadoop-1 itself. Until we can 
come up with a naming scheme and the related build changes so that the 
artifacts for hadoop-1 and 2 can exist simultaneously - we probably should 
stick to just releasing the 1.0 compatible artifacts. 


Thanks,
Hari


On Thursday, June 12, 2014 at 8:04 PM, Roshan Naik wrote:

> Will the released binaries be built with the new -Dhadoop.profile=hbase-98
> option ?
> 
> 
> On Wed, Jun 11, 2014 at 8:54 AM, Ashish <[email protected] 
> (mailto:[email protected])> wrote:
> 
> > +1
> > 
> > Build works good and all tests pass
> > 
> > 
> > On Wed, Jun 11, 2014 at 4:10 AM, Hari Shreedharan <
> > [email protected] (mailto:[email protected])
> > > 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
> > > 
> > 
> > 
> > 
> > 
> > --
> > thanks
> > ashish
> > 
> > Blog: http://www.ashishpaliwal.com/blog
> > My Photo Galleries: http://www.pbase.com/ashishpaliwal
> > 
> 
> 
> -- 
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to 
> which it is addressed and may contain information that is confidential, 
> privileged and exempt from disclosure under applicable law. If the reader 
> of this message is not the intended recipient, you are hereby notified that 
> any printing, copying, dissemination, distribution, disclosure or 
> forwarding of this communication is strictly prohibited. If you have 
> received this communication in error, please contact the sender immediately 
> and delete it from your system. Thank You.
> 
> 


Reply via email to