Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (nike.apache.org: 98.139.253.105 is neither permitted
 nor denied by domain of thiruvel@yahoo-inc.com)
From: Thiruvel Thirumoolan <thiruvel@yahoo-inc.com>
To: "oozie-dev@incubator.apache.org" <oozie-dev@incubator.apache.org>,
        "oozie-users@incubator.apache.org" <oozie-users@incubator.apache.org>
CC: "general@incubator.apache.org" <general@incubator.apache.org>
Date: Mon, 20 Feb 2012 19:02:26 +0530
Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2)
Thread-Topic: [VOTE] Release Oozie 3.1.3 (candidate 2)
Thread-Index: Aczv1BatvFr4rLVMTxu78ByiUSP6Jg==
Message-ID: <CB684804.15F4A%thiruvel@yahoo-inc.com>
In-Reply-To: <84022490-EEBB-4D6C-A3A2-370F1D161FDD@yahoo.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

+1 (non-binding from a user).

Downloaded sources and ran bin/mkdistro.sh 2 times. All tests went through
fine no my RHEL 5.x
Deployed the distro using oozie-setup.sh on a single node un-secure Hadoop
20.205 cluster and launched a co-ordinator with about 20+ workflows. All
workflows completed as expected.

Thanks for all the hard work,

-Thiruvel

On 2/20/12 3:19 AM, "Mohamed Battisha" <mbattish@yahoo.com> wrote:

>+1
>Downloaded the source and ran the unit test
>
>Everything looks fine
>
>Thanks!
>Mohamed
>
>On Feb 18, 2012, at 2:54 PM, Jeremy Hanna wrote:
>
>> +1 (non-binding from a user/contributor) - pulled down the artifacts
>>and did the maven tests on them.  Got it to complete, but on one of the
>>test runs I got test failures for TestPauseTransitService and
>>TestSshActionExecutor.  I think those may need to just be looked at for
>>completion consistency and not anything to do with the code their
>>testing.
>>=20
>> On Feb 17, 2012, at 1:59 PM, Mayank Bansal wrote:
>>=20
>>> +1
>>>=20
>>> looks good.
>>>=20
>>> Thanks,
>>> Mayank
>>>=20
>>> On Fri, Feb 17, 2012 at 3:38 AM, Chris Douglas <cdouglas@apache.org>
>>>wrote:
>>>=20
>>>> 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?
>>>>=20
>>>> Yes
>>>>=20
>>>>> 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
>>>>=20
>>>> 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
>>>>=20
>>>>> Regards,
>>>>> Mohammad
>>>>>=20
>>>>>=20
>>>>> ________________________________
>>>>> From: Chris Douglas <cdouglas@apache.org>
>>>>> To: oozie-dev@incubator.apache.org
>>>>> Cc: Mohammad Islam <mislam77@yahoo.com>; "
>>>> oozie-users@incubator.apache.org" <oozie-users@incubator.apache.org>
>>>>> Sent: Thursday, February 16, 2012 11:13 PM
>>>>> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2)
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> 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.).
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> 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
>>>>>=20
>>>>> On Thu, Feb 16, 2012 at 9:22 PM, Alejandro Abdelnur
>>>>><tucu@cloudera.com>
>>>> wrote:
>>>>>> Chris,
>>>>>>=20
>>>>>> I'm a bit confused here, I've thought that the significant votes
>>>>>>where
>>>> from
>>>>>> the IPMC.
>>>>>>=20
>>>>>> I guess most of the committers/contributors thought along the same
>>>> lines.
>>>>>>=20
>>>>>> Thxs.
>>>>>>=20
>>>>>> Alejandro
>>>>>>=20
>>>>>> On Thu, Feb 16, 2012 at 5:39 PM, Chris Douglas <cdouglas@apache.org>
>>>> wrote:
>>>>>>=20
>>>>>>> The vote didn't attract any votes from contributors. As far as I
>>>>>>>know,
>>>>>>> none of the voters in this thread actually develop Oozie.
>>>>>>>=20
>>>>>>> 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
>>>>>>>=20
>>>>>>> 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.
>>>>>>>>=20
>>>>>>>> Special thanks to mentors who gave their valuable feedback to
>>>>>>>>make it
>>>>>>> better.
>>>>>>>> I also want to mention Alejandro and Virag who helped to make the
>>>> whole
>>>>>>> process smoother.
>>>>>>>> Now I will ask for vote in general@incubator
>>>>>>>>=20
>>>>>>>> Regards,
>>>>>>>> Moahmmad
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> ________________________________
>>>>>>>> From: Devaraj Das <ddas@hortonworks.com>
>>>>>>>> To: oozie-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)
>>>>>>>>=20
>>>>>>>> I ran the tests and also inspected the top level txt files. Looks
>>>> good.
>>>>>>>>=20
>>>>>>>> +1 for the release.
>>>>>>>>=20
>>>>>>>> On Feb 13, 2012, at 4:43 PM, Mohammad Islam wrote:
>>>>>>>>=20
>>>>>>>>> Hi,
>>>>>>>>>=20
>>>>>>>>> Thanks everyone for giving valuable comments for the RC0 and RC1.
>>>>>>>>>=20
>>>>>>>>> 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:
>>>>>>>>>=20
>>>>>>>>> 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
>>>> subdirectory
>>>>>>> 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)
>>>>>>>>>=20
>>>>>>>>> Keys used to sign the release are available at
>>>>>>>=20
>>>>>>>http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=3Dmarku=
p.
>>>>>>>>>=20
>>>>>>>>> Please download, test, and try it out from here:
>>>>>>>>>=20
>>>>>>>>>=20
>>>> http://people.apache.org/~kamrul/oozie-3.1.3-incubating-candidate-2/
>>>>>>>>>=20
>>>>>>>>> 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 from the release was
>>>> created
>>>>>>> could be found at :
>>>>>>>>>=20
>>>>>>>=20
>>>>=20
>>>>https://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc2
>>>>/
>>>>>>>>>=20
>>>>>>>>> Should we release this? Vote closes on Feb 15th.
>>>>>>>>>=20
>>>>>>>>> Regards,
>>>>>>>>> Mohammad
>>>>>>>=20
>>>>=20
>>=20
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org