In the past we've carried it out on common-dev: http://hadoop-common.472056.n3.nabble.com/VOTE-Release-Hadoop-0-21-0-candidate-2-td1181981.html
Arun On Jul 28, 2011, at 5:33 PM, <milind.bhandar...@emc.com> wrote: > Somehow I remember that the 0.20.203.0 vote was carried out on general@ > > Here is a message from the archive: > > http://mail-archives.apache.org/mod_mbox/hadoop-general/201105.mbox/browser > > - milind > > --- > Milind Bhandarkar > > > -----Original Message----- > From: Arun C Murthy [mailto:a...@hortonworks.com] > Sent: Thursday, July 28, 2011 5:27 PM > To: common-dev@hadoop.apache.org > Subject: Re: [VOTE] Release 0.20.204.0-rc0 > > Nope. general@ is only for announcements. > > AFAIK Votes are developer activities. > > Arun > > On Jul 28, 2011, at 5:11 PM, Aaron T. Myers wrote: > >> Shouldn't this vote be taking place on general@, instead of common-dev@? I'm >> under the impression that that is where all votes are supposed to take >> place. Please correct me if I am wrong about that. >> >> -- >> Aaron T. Myers >> Software Engineer, Cloudera >> >> >> >> On Thu, Jul 28, 2011 at 5:02 PM, Giridharan Kesavan >> <gkesa...@yahoo-inc.com>wrote: >> >>> This issue is fixed with Eric's patch for HADOOP-7356. Since Owen is out on >>> vacation Iam working on getting the release tarball. >>> >>> -Giri >>> >>> >>> On 7/28/11 1:56 PM, "Giridharan Kesavan" <gkesa...@yahoo-inc.com> wrote: >>> >>>> Myself and Eric Yang are looking into this. >>>> -Giri >>>> >>>> On 7/28/11 12:04 PM, "Allen Wittenauer" <awittena...@linkedin.com> >>> wrote: >>>> >>>>> >>>>> On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: >>>>> >>>>>> I've created a release candidate for 0.20.204.0 that I would like to >>>>>> release. >>>>>> >>>>>> It is available at: >>> http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ >>>>>> >>>>>> 0.20.204.0 has many fixes including disk fail in place and the new rpm >>> and >>>>>> deb packages. Fail in place allows the DataNode and TaskTracker to >>> continue >>>>>> after a hard drive fails. >>>>> >>>>> >>>>> Is it still failing to build according to Jenkins? >>>>> >>>> >>> >>> > >
