Sorry Ralph. This vote was cancelled for that exact issue. There's a new RC up that fixes this.
On Fri, Dec 30, 2011 at 4:11 PM, Ralph Goers <[email protected]>wrote: > I've downloaded the source and noticed that the tar contains a directory > named flume-1.0.0-SNAPSHOT and that the artifact below also contains > SNAPSHOT in the name. This makes me wonder just what we are voting on since > this obviously cannot be the actual release. What is the process that is > being followed? In commons there are at least two variations. The one I > typically follow is to use the release plugin and deploy the artifacts to > the Apache staging repo. Others follow a process closer to this one that > involves renaming the artifact and changing the tag from an rc to a real > release once the vote changes. > > Ralph > > On Dec 30, 2011, at 3:07 PM, Eric Sammer wrote: > > > This vote is being called on [email protected] and > > [email protected] concurrently. > > > > This is the first incubator release for Apache Flume, version > > 1.0.0-incubating. > > > > It fixes the following issues: > > http://bit.ly/sj5Fh8 > > > > *** Please download, test and vote by January 1st, 2012. > > > > Note that we are voting upon the source (tag), binaries are provided > > for convenience. > > > > Source files, signature, and checksums: > > > http://people.apache.org/~esammer/flume/flume-1.0.0-SNAPSHOT-incubating-rc3/ > > > > The tag to be voted upon: > > http://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.0.0-rc3/ > > > > Flume's KEYS file containing PGP keys we use to sign the release: > > http://svn.apache.org/repos/asf/incubator/flume/dist/KEYS > > > > Note that the Incubator PMC needs to vote upon the release after a > > successful PPMC vote before any release can be made official. > > > > -- > > Eric Sammer > > twitter: esammer > > data: www.cloudera.com > > -- Eric Sammer twitter: esammer data: www.cloudera.com
