incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohammad Islam <>
Subject Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Date Mon, 06 Feb 2012 23:04:33 GMT
Hi Chris,

>These should show up at the top level, with a DISCLAIMER file.

Are you asking to add a  new DISCLAIMER file with that text?


----- Original Message -----
From: Chris Douglas <>
Cc:; Mohammad Islam <>;
Sent: Monday, February 6, 2012 11:16 AM
Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 0)

On Mon, Feb 6, 2012 at 8:51 AM, Roman Shaposhnik <> wrote:
>   1. this appears to be a binary tarball containing no source files. As far
>   as Apache release go -- the tarball is supposed to be a source tarball
>   with an additional option of convenience binary artifact either in the same
>   tarball or alongside with it.

+1; binary artifacts are usually rolled after a source release has
passed a vote (the code is what's being voted on, not the binary).
That said, the LICENSE and NOTICE files look good for the binary
tarball. These should show up at the top level, with a DISCLAIMER


Apache Oozie is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC.

Incubation is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF projects.

While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

For more information about the incubation status of the Oozie project you
can go to the following page:


>   2. the name of the tarball and top level subdirectory has to be a full
>   version. For an apache incubating project the full version would be
>   oozie-3.1.3-incubating. This has to be reflected in the name of the
>   source tarball and POMs.

+1 -C

>   3. it appears that your assembly plugin inserted an extra '/' between
>   oozie-3.1.3/ and 'docs' subdirectory. this results in a weird unpacking
>   errors with some of the tar's and GUI programs.
> If you could, please, fix the above issues, I'd be more than happy to
> proceed with integration testing of the RC inside of Bigtop.
> Thanks,
> Roman.
> On Mon, Feb 6, 2012 at 1:05 AM, Mohammad Islam <> wrote:
>> Hi,
>>>I have created a candidate build for Oozie-3.1.3. This is the first release of
Oozie from Apache Incubation.
>>>Keys used to sign the release are available at
>>>Please download, test, and try it out:
>>>The release log, md5 signature, gpg signature, and rat report can all be found
at the above link.
>> The release candidate source tag could be found at:
>> It is tagged from this branch:
>> Should we release this? Vote closes on Feb 8th.

View raw message