in step 3 under building you say "Tar/GZ the release directory as zookeeper-X.Y.Z.tar.gz". the release directory refers the directory you untared the tar.gz file into in step 2. right?
ben On Tue, Feb 22, 2011 at 9:02 AM, Patrick Hunt <ph...@apache.org> wrote: > Done. (hopefully this gives you some insight into why I've been > pushing for maven, not perfect but it does alot of this for you). > > Patrick > > On Tue, Feb 22, 2011 at 7:58 AM, Benjamin Reed <br...@apache.org> wrote: > > pat, do you mind updating the building section of > > https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease > > <https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease>with > > these three items. signing the jar files is very unclear in the original > > doc. do i untar, sign, and retar? we don't do jarsigning? > > > > i'll do an rc1 this evening. > > > > ben > > > > On Mon, Feb 21, 2011 at 11:55 PM, Patrick Hunt <ph...@apache.org> wrote: > > > >> -1, in general looks good but I did notice a few things: > >> > >> * the "zookeeper_version.h" file needs to be updated to version 3.3.3 > >> * same with configure.ac ( > >> http://wiki.apache.org/hadoop/ZooKeeper/HowToRelease) > >> * the toplevel zk jar and all jars in dist-maven have not been signed, > >> they need to be > >> > >> RAT passed so that's good. > >> > >> Patrick > >> > >> On Sat, Feb 19, 2011 at 6:27 AM, Benjamin Reed <br...@apache.org> > wrote: > >> > (the previous email had the URL slightly incorrect) > >> > > >> > after much struggle! i've created a candidate build for ZooKeeper > 3.3.3. > >> > this is a bug fix > >> > release addressing 13 issues (two of them extremely critical) -- see > the > >> > release notes for details. > >> > > >> > *** Please download, test and VOTE before the > >> > *** vote closes 11pm pacific time, Tuesday, February 22.*** > >> > > >> > http://people.apache.org/~breed/zookeeper-3.3.3-candidate-0/ > >> > > >> > one thing that has not been fixed in this release is that the docs > still > >> > reference hadoop. this will be fixed in a future release. > >> > > >> > should we release this? > >> > > >> > ben > >> > > >> > ps - give that this is the first release there is more than likely > >> something > >> > i missed and given the severity of issues addressed it would be nice > to > >> get > >> > it out quickly. please review ASAP. > >> > > >> > > >
