From general-return-34501-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Sat Feb 18 19:56:42 2012 Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1E46496D5 for ; Sat, 18 Feb 2012 19:56:42 +0000 (UTC) Received: (qmail 37377 invoked by uid 500); 18 Feb 2012 19:56:41 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 37199 invoked by uid 500); 18 Feb 2012 19:56:41 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Delivered-To: moderator for general@incubator.apache.org Received: (qmail 52738 invoked by uid 99); 17 Feb 2012 23:16:22 -0000 X-ASF-Spam-Status: No, hits=2.6 required=5.0 tests=HTML_FONT_SIZE_LARGE,HTML_MESSAGE,NO_RDNS_DOTCOM_HELO,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.145.54.173 is neither permitted nor denied by domain of chitnis@yahoo-inc.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1329520547; bh=a2v88/zPAzTE3+lOkvLh9xALpcLctpHmfXFMt+XGG/U=; h=From:To:CC:Date:Subject:Message-ID:In-Reply-To:Content-Type: MIME-Version; b=b2usS4DGZgnRJxPE+KPNvF1CpzNNzpoiN27xzS/h73M92pTG70dk5umICqMoxTT8k Mds0LrQ7rZYw64Gr2U37CJUUy/qRY+Jy6L2n4BVAza/RFS+SZruYYOCf/xDh+nPUUQ 2y0NiBIZzGXrpWDg6Tc0bqqEMGVxupb7nV2jc5tY= From: Mona Chitnis To: "oozie-dev@incubator.apache.org" CC: Mohammad Islam , "general@incubator.apache.org" Date: Fri, 17 Feb 2012 15:19:46 -0800 Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) Thread-Topic: [VOTE] Release Oozie 3.1.3 (candidate 2) Thread-Index: AcztxquYSzpWuYUgTSCpstrwjdYGbwAA/dfP Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: user-agent: Microsoft-Entourage/13.8.0.101117 acceptlanguage: en-US Content-Type: multipart/related; boundary="_004_CB6420922C1Fchitnisyahooinccom_"; type="multipart/alternative" MIME-Version: 1.0 --_004_CB6420922C1Fchitnisyahooinccom_ Content-Type: multipart/alternative; boundary="_000_CB6420922C1Fchitnisyahooinccom_" --_000_CB6420922C1Fchitnisyahooinccom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable For me too, org.apache.oozie.service.TestPauseTransitService passed on 1 re= try. +1 on the release. Great job! Mona On 2/17/12 2:50 PM, "Harsh J" wrote: +1 on rc2 (ccb3e271892d6e69881eb3785ef2bc3c). (On OSX) - Downloaded, ran bin/mkdistro.sh and it ended in a success after one retry. (Test org.apache.oozie.service.TestPauseTransitService seems a little flaky, but may be just me, cause eventual runs of that specific test all passed - it just failed on my first run). On Sat, Feb 18, 2012 at 1:37 AM, Virag Kothari wrote: > Hi, > > Downloaded the source, ran the test cases - all works fine! > +1 > > Thanks, > Virag > > On 2/17/12 3:38 AM, "Chris Douglas" wrote: > >> On Fri, Feb 17, 2012 at 12:50 AM, Mohammad Islam wr= ote: >>> Hi Chris, >>> So can the other contributors/committers VOTE now? >> >> Yes >> >>> As oozie-user VOTE is already closed, what would be the best option at = this >>> stage? >>> 1. Go to genenral@incubator and vote there. >>> 2. Vote in the same threadat oozie-user >> >> Might as well show support/express reservations on the >> general@incubator thread so it's in one place. IIRC the general@ >> thread cc'd oozie-dev. -C >> >>> Regards, >>> Mohammad >>> >>> >>> ________________________________ >>> From: Chris Douglas >>> To: oozie-dev@incubator.apache.org >>> Cc: Mohammad Islam ; "oozie-users@incubator.apache.= org" >>> >>> Sent: Thursday, February 16, 2012 11:13 PM >>> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) >>> >>> That's a pretty dire error in the documentation if that's the >>> impression. Projects (and podlings) are responsible for their code, >>> community, and releases. The PPMC certifies that the artifact >>> represents an iteration of its progress by voting on a release in some >>> series, just as a PMC does. >>> >>> The IPMC has a functionary, mundane role. It's supposed to make >>> cursory checks: code being released respects the licensing >>> requirements of dependencies, notices give accurate guidance to >>> downstream consumers of that code, etc. Since the ASF is releasing >>> that code under license, the idea is that IPMC members protect the >>> foundation from common misunderstandings (e.g. if a podling thought >>> they could release GPL'd code, someone else's code, etc.). >>> >>> Once the project has some experience with releases, a clear >>> understanding of what the ASF wants w.r.t. community, etc. then >>> podling graduates. Before that, the voting guidelines are necessary >>> because the IPMC members are acting on behalf of the foundation. The >>> vote from the PPMC expresses that the artifact represents their >>> output. The vote from the IPMC certifies that the artifact won't get >>> the ASF into legal trouble. >>> >>> Release votes are a strict majority per ASF bylaws. AFAICT, asserting >>> that the IPMC votes are the only ones that are binding in the second >>> round is just adding a layer of indirection to solve a counting >>> problem. -C >>> >>> On Thu, Feb 16, 2012 at 9:22 PM, Alejandro Abdelnur >>> wrote: >>>> Chris, >>>> >>>> I'm a bit confused here, I've thought that the significant votes where= from >>>> the IPMC. >>>> >>>> I guess most of the committers/contributors thought along the same lin= es. >>>> >>>> Thxs. >>>> >>>> Alejandro >>>> >>>> On Thu, Feb 16, 2012 at 5:39 PM, Chris Douglas w= rote: >>>> >>>>> The vote didn't attract any votes from contributors. As far as I know= , >>>>> none of the voters in this thread actually develop Oozie. >>>>> >>>>> The IPMC vote is a check on the podling's compliance with licensing >>>>> and other foundation-level practices. It's far, far less significant >>>>> than the community's appraisal of the release itself. Would the PPMC >>>>> please weigh in? -C >>>>> >>>>> On Thu, Feb 16, 2012 at 2:47 PM, Mohammad Islam >>>>> wrote: >>>>>> Hi All, >>>>>> As 72 hours has passed, I would like to close the vote. >>>>>> The proposed RC-2 got three +1s from three mentors without -1 or 0. >>>>>> >>>>>> Special thanks to mentors who gave their valuable feedback to make i= t >>>>> better. >>>>>> I also want to mention Alejandro and Virag who helped to make the wh= ole >>>>> process smoother. >>>>>> Now I will ask for vote in general@incubator >>>>>> >>>>>> Regards, >>>>>> Moahmmad >>>>>> >>>>>> >>>>>> ________________________________ >>>>>> From: Devaraj Das >>>>>> To: oozie-dev@incubator.apache.org >>>>>> Cc: Oozie-users >>>>>> Sent: Tuesday, February 14, 2012 9:42 PM >>>>>> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) >>>>>> >>>>>> I ran the tests and also inspected the top level txt files. Looks go= od. >>>>>> >>>>>> +1 for the release. >>>>>> >>>>>> On Feb 13, 2012, at 4:43 PM, Mohammad Islam wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Thanks everyone for giving valuable comments for the RC0 and RC1. >>>>>>> >>>>>>> I created a new candidate (RC2) build for Oozie-3.1.3 incorporating >>>>> most of the comments (including Chris's finding). >>>>>>> The following JIRAs were resolved based on the comments: >>>>>>> >>>>>>> OOZIE-694 Update the Install and Quick start guide with appropriate >>>>> hadoop versions for branch-3.1 (Mohammad) >>>>>>> OOZIE-602 Update the Hadoop version to be an Apache Hadoop version >>>>> (tucu) >>>>>>> OOZIE-689 XTestCase proxyuser settings fails with Hadoop 1.0.0/0.23= .1 >>>>> (tucu) >>>>>>> OOZIE-601 Oozie's POMs should use org.apache.oozie as group (tucu) >>>>>>> OOZIE-685 Update License file with 3rd party license information. >>>>> (Mohammad) >>>>>>> OOZIE-682 Update version 3.1.3 to 3.1.3-incubating in all >>>>> pom.xml.(Mohammad) >>>>>>> OOZIE-683 Add DISCLAIMER file in the root.(Mohammad) >>>>>>> OOZIE-681 Update readme.txt contents.(Mohammad) >>>>>>> OOZIE-680 oozie's assembly creates an extra level of empty subdirec= tory >>>>> for docs. (rvs via tucu) >>>>>>> OOZIE-608 testCoordChangeEndTime and testCoordChangeXCommand are >>>>> failing(Mohamed). >>>>>>> OOZIE-678 Update NOTICE.txt to reflect the workcount binaries into >>>>> oozie src(Mohammad) >>>>>>> >>>>>>> Keys used to sign the release are available at >>>>> http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=3Dmarkup= . >>>>>>> >>>>>>> Please download, test, and try it out from here: >>>>>>> >>>>>>> http://people.apache.org/~kamrul/oozie-3.1.3-incubating-candidate-2= / >>>>>>> >>>>>>> The release log, md5 signature, gpg signature, and rat report all c= an >>>>> be found at the above link. >>>>>>> In case, anyone is interested, the svn tag from the release was cre= ated >>>>> could be found at : >>>>>>> >>>>> https://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-r= c2/ >>>>>>> >>>>>>> Should we release this? Vote closes on Feb 15th. >>>>>>> >>>>>>> Regards, >>>>>>> Mohammad >>>>> > -- mona chitnis software developer chitnis@yahoo-inc.com direct 408-336-7908 mobile 864-650-0100 701 first avenue, sunnyvale, ca, 94089-0703, us phone (408) 349 3300 fax (408) 349 3301 [cid:3412336786_2051424] --_000_CB6420922C1Fchitnisyahooinccom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [VOTE] Release Oozie 3.1.3 (candidate 2) For me too, org.apache.oozie.service= .TestPauseTransitService passed on 1 retry.

+1 on the release. Great job!

Mona


On 2/17/12 2:50 PM, "Harsh J" <= harsh@cloudera.com> wrote:

+1 on rc2 (ccb3e271892d6e69881= eb3785ef2bc3c).

(On OSX) - Downloaded, ran bin/mkdistro.sh and it ended in a success
after one retry.

(Test org.apache.oozie.service.TestPauseTransitService seems a little
flaky, but may be just me, cause eventual runs of that specific test
all passed - it just failed on my first run).

On Sat, Feb 18, 2012 at 1:37 AM, Virag Kothari <virag@yahoo-inc.com> wrote:
> Hi,
>
> Downloaded the source, ran the test cases - all works fine!
> +1
>
> Thanks,
> Virag
>
> On 2/17/12 3:38 AM, "Chris Douglas" <cdouglas@apache.org> wrote:
>
>> On Fri, Feb 17, 2012 at 12:50 AM, Mohammad Islam <mislam77@yahoo.com> wrote:
>>> Hi Chris,
>>> So can the other contributors/committers VOTE now?
>>
>> Yes
>>
>>> As oozie-user VOTE is already closed, what would be the best o= ption at this
>>> stage?
>>> 1. Go to genenral@incubator and vote there.
>>> 2. Vote in the same threadat oozie-user
>>
>> Might as well show support/express reservations on the
>> general@incubator thread so it's in one place. IIRC the general@ >> thread cc'd oozie-dev. -C
>>
>>> Regards,
>>> Mohammad
>>>
>>>
>>> ________________________________
>>> From: Chris Douglas <cdougl= as@apache.org>
>>> To: oozie-dev@incub= ator.apache.org
>>> Cc: Mohammad Islam <mislam77= @yahoo.com>; "oozi= e-users@incubator.apache.org"
>>> <oozie-users@i= ncubator.apache.org>
>>> Sent: Thursday, February 16, 2012 11:13 PM
>>> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2)
>>>
>>> That's a pretty dire error in the documentation if that's the<= BR> >>> impression. Projects (and podlings) are responsible for their = code,
>>> community, and releases. The PPMC certifies that the artifact<= BR> >>> represents an iteration of its progress by voting on a release= in some
>>> series, just as a PMC does.
>>>
>>> The IPMC has a functionary, mundane role. It's supposed to mak= e
>>> cursory checks: code being released respects the licensing
>>> requirements of dependencies, notices give accurate guidance t= o
>>> downstream consumers of that code, etc. Since the ASF is relea= sing
>>> that code under license, the idea is that IPMC members protect= the
>>> foundation from common misunderstandings (e.g. if a podling th= ought
>>> they could release GPL'd code, someone else's code, etc.).
>>>
>>> Once the project has some experience with releases, a clear >>> understanding of what the ASF wants w.r.t. community, etc. the= n
>>> podling graduates. Before that, the voting guidelines are nece= ssary
>>> because the IPMC members are acting on behalf of the foundatio= n. The
>>> vote from the PPMC expresses that the artifact represents thei= r
>>> output. The vote from the IPMC certifies that the artifact won= 't get
>>> the ASF into legal trouble.
>>>
>>> Release votes are a strict majority per ASF bylaws. AFAICT, as= serting
>>> that the IPMC votes are the only ones that are binding in the = second
>>> round is just adding a layer of indirection to solve a countin= g
>>> problem. -C
>>>
>>> On Thu, Feb 16, 2012 at 9:22 PM, Alejandro Abdelnur <tucu@cloudera.com>
>>> wrote:
>>>> Chris,
>>>>
>>>> I'm a bit confused here, I've thought that the significant= votes where from
>>>> the IPMC.
>>>>
>>>> I guess most of the committers/contributors thought along = the same lines.
>>>>
>>>> Thxs.
>>>>
>>>> Alejandro
>>>>
>>>> On Thu, Feb 16, 2012 at 5:39 PM, Chris Douglas <cdouglas@apache.org> wrote:
>>>>
>>>>> The vote didn't attract any votes from contributors. A= s far as I know,
>>>>> none of the voters in this thread actually develop Ooz= ie.
>>>>>
>>>>> The IPMC vote is a check on the podling's compliance w= ith licensing
>>>>> and other foundation-level practices. It's far, far le= ss significant
>>>>> than the community's appraisal of the release itself. = Would the PPMC
>>>>> please weigh in? -C
>>>>>
>>>>> On Thu, Feb 16, 2012 at 2:47 PM, Mohammad Islam <mislam77@yahoo.com>
>>>>> wrote:
>>>>>> Hi All,
>>>>>> As 72 hours has passed, I would like to close the = vote.
>>>>>> The proposed RC-2 got three +1s from three mentors= without -1 or 0.
>>>>>>
>>>>>> Special thanks to mentors who gave their valuable = feedback to make it
>>>>> better.
>>>>>> I also want to mention Alejandro and Virag who hel= ped to make the whole
>>>>> process smoother.
>>>>>> Now I will ask for vote in general@incubator
>>>>>>
>>>>>> Regards,
>>>>>> Moahmmad
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>> From: Devaraj Das <ddas@hortonworks.com>
>>>>>> To: ooz= ie-dev@incubator.apache.org
>>>>>> Cc: Oozie-users <oozie-users@incubator.apache.org>
>>>>>> Sent: Tuesday, February 14, 2012 9:42 PM
>>>>>> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate= 2)
>>>>>>
>>>>>> I ran the tests and also inspected the top level t= xt files. Looks good.
>>>>>>
>>>>>> +1 for the release.
>>>>>>
>>>>>> On Feb 13, 2012, at 4:43 PM, Mohammad Islam wrote:=
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Thanks everyone for giving valuable comments f= or the RC0 and RC1.
>>>>>>>
>>>>>>> I created a new candidate (RC2) build for Oozi= e-3.1.3 incorporating
>>>>> most of the comments (including Chris's finding).
>>>>>>> The following JIRAs were resolved based on the= comments:
>>>>>>>
>>>>>>> OOZIE-694 Update the Install and Quick start g= uide with appropriate
>>>>> hadoop versions for branch-3.1 (Mohammad)
>>>>>>> OOZIE-602 Update the Hadoop version to be an A= pache Hadoop version
>>>>> (tucu)
>>>>>>> OOZIE-689 XTestCase proxyuser settings fails w= ith Hadoop 1.0.0/0.23.1
>>>>> (tucu)
>>>>>>> OOZIE-601 Oozie's POMs should use org.apache.o= ozie as group (tucu)
>>>>>>> OOZIE-685 Update License file with 3rd party l= icense information.
>>>>> (Mohammad)
>>>>>>> OOZIE-682 Update version 3.1.3 to 3.1.3-incuba= ting in all
>>>>> pom.xml.(Mohammad)
>>>>>>> OOZIE-683 Add DISCLAIMER file in the root.(Moh= ammad)
>>>>>>> OOZIE-681 Update readme.txt contents.(Mohammad= )
>>>>>>> OOZIE-680 oozie's assembly creates an extra le= vel of empty subdirectory
>>>>> for docs. (rvs via tucu)
>>>>>>> OOZIE-608 testCoordChangeEndTime and testCoord= ChangeXCommand are
>>>>> failing(Mohamed).
>>>>>>> OOZIE-678 Update NOTICE.txt to reflect the wor= kcount binaries into
>>>>> oozie src(Mohammad)
>>>>>>>
>>>>>>> Keys used to sign the release are available at=
>>>>> http://svn.apache.org/viewvc/incubator/oozie/tr= unk/KEYS?view=3Dmarkup.
>>>>>>>
>>>>>>> Please download, test, and try it out from her= e:
>>>>>>>
>>>>>>> http://people.apache.org/~kamrul/oozie-3= .1.3-incubating-candidate-2/
>>>>>>>
>>>>>>> The release log, md5 signature, gpg signature,= and rat report all can
>>>>> be found at the above link.
>>>>>>> In case, anyone is interested, the svn tag fro= m the release was created
>>>>> could be found at :
>>>>>>>
>>>>> https://svn.apache.org/repos/asf/incubator/o= ozie/tags/release-3.1.3-rc2/
>>>>>>>
>>>>>>> Should we release this? Vote closes on Feb 15t= h.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mohammad
>>>>>
>



--
mona
chitni= s
software developer
=A0
chitnis@yahoo-inc.com
direct 408-336-7908=A0=A0=A0= =A0mobile 864-650-0100
=A0
701 fi= rst avenue, sunnyvale, ca, 94089-0703, us
phone (408) 349 3300=A0=A0=A0= =A0fax (408) 349 3301

=
--_000_CB6420922C1Fchitnisyahooinccom_-- --_004_CB6420922C1Fchitnisyahooinccom_--