You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by Mohammad Islam <mi...@yahoo.com> on 2012/02/06 10:05:02 UTC
[VOTE] Release Oozie 3.1.3 (candidate 0)
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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>
>Please download, test, and try it out:
>
>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>
>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:
http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>
It is tagged from this branch:
http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>
>
Should we release this? Vote closes on Feb 8th.
>
>Regards,
>Mohammad
>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Devaraj,
I will take care of that.
Regards,
Mohammad
----- Original Message -----
From: Devaraj Das <dd...@hortonworks.com>
To: oozie-dev@incubator.apache.org
Cc: oozie-users@incubator.apache.org; Mohammad Islam <mi...@yahoo.com>; bigtop-dev@incubator.apache.org
Sent: Monday, February 6, 2012 11:40 AM
Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Also does it make sense to cleanup the readme.txt (lots of references to yahoo there) in the top-level directory before releasing.. (I don't think this is a must but if we are restarting the vote then maybe ?)..
On Feb 6, 2012, at 11:16 AM, Chris Douglas wrote:
> On Mon, Feb 6, 2012 at 8:51 AM, Roman Shaposhnik <rv...@apache.org> 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
> file:
>
> ----
>
> 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:
>
> http://incubator.apache.org/oozie
>
> ----
>
>> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>>
>>>> Please download, test, and try it out:
>>>>
>>>> http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>>
>>>> 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:
>>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>>
>>> It is tagged from this branch:
>>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>>
>>>
>>>>
>>> Should we release this? Vote closes on Feb 8th.
>>>
>>>>
>>>> Regards,
>>>> Mohammad
>>>
>>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Devaraj,
I will take care of that.
Regards,
Mohammad
----- Original Message -----
From: Devaraj Das <dd...@hortonworks.com>
To: oozie-dev@incubator.apache.org
Cc: oozie-users@incubator.apache.org; Mohammad Islam <mi...@yahoo.com>; bigtop-dev@incubator.apache.org
Sent: Monday, February 6, 2012 11:40 AM
Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Also does it make sense to cleanup the readme.txt (lots of references to yahoo there) in the top-level directory before releasing.. (I don't think this is a must but if we are restarting the vote then maybe ?)..
On Feb 6, 2012, at 11:16 AM, Chris Douglas wrote:
> On Mon, Feb 6, 2012 at 8:51 AM, Roman Shaposhnik <rv...@apache.org> 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
> file:
>
> ----
>
> 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:
>
> http://incubator.apache.org/oozie
>
> ----
>
>> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>>
>>>> Please download, test, and try it out:
>>>>
>>>> http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>>
>>>> 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:
>>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>>
>>> It is tagged from this branch:
>>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>>
>>>
>>>>
>>> Should we release this? Vote closes on Feb 8th.
>>>
>>>>
>>>> Regards,
>>>> Mohammad
>>>
>>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Devaraj Das <dd...@hortonworks.com>.
Also does it make sense to cleanup the readme.txt (lots of references to yahoo there) in the top-level directory before releasing.. (I don't think this is a must but if we are restarting the vote then maybe ?)..
On Feb 6, 2012, at 11:16 AM, Chris Douglas wrote:
> On Mon, Feb 6, 2012 at 8:51 AM, Roman Shaposhnik <rv...@apache.org> 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
> file:
>
> ----
>
> 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:
>
> http://incubator.apache.org/oozie
>
> ----
>
>> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>>
>>>> Please download, test, and try it out:
>>>>
>>>> http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>>
>>>> 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:
>>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>>
>>> It is tagged from this branch:
>>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>>
>>>
>>>>
>>> Should we release this? Vote closes on Feb 8th.
>>>
>>>>
>>>> Regards,
>>>> Mohammad
>>>
>>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
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?
Regards,
Mohammad
----- Original Message -----
From: Chris Douglas <cd...@apache.org>
To: oozie-dev@incubator.apache.org
Cc: oozie-users@incubator.apache.org; Mohammad Islam <mi...@yahoo.com>; bigtop-dev@incubator.apache.org
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 <rv...@apache.org> 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
file:
----
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:
http://incubator.apache.org/oozie
----
> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>
>>>Please download, test, and try it out:
>>>
>>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>
>>>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:
>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>
>> It is tagged from this branch:
>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>
>>
>>>
>> Should we release this? Vote closes on Feb 8th.
>>
>>>
>>>Regards,
>>>Mohammad
>>
>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Devaraj Das <dd...@hortonworks.com>.
Also does it make sense to cleanup the readme.txt (lots of references to yahoo there) in the top-level directory before releasing.. (I don't think this is a must but if we are restarting the vote then maybe ?)..
On Feb 6, 2012, at 11:16 AM, Chris Douglas wrote:
> On Mon, Feb 6, 2012 at 8:51 AM, Roman Shaposhnik <rv...@apache.org> 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
> file:
>
> ----
>
> 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:
>
> http://incubator.apache.org/oozie
>
> ----
>
>> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>>
>>>> Please download, test, and try it out:
>>>>
>>>> http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>>
>>>> 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:
>>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>>
>>> It is tagged from this branch:
>>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>>
>>>
>>>>
>>> Should we release this? Vote closes on Feb 8th.
>>>
>>>>
>>>> Regards,
>>>> Mohammad
>>>
>>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
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?
Regards,
Mohammad
----- Original Message -----
From: Chris Douglas <cd...@apache.org>
To: oozie-dev@incubator.apache.org
Cc: oozie-users@incubator.apache.org; Mohammad Islam <mi...@yahoo.com>; bigtop-dev@incubator.apache.org
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 <rv...@apache.org> 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
file:
----
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:
http://incubator.apache.org/oozie
----
> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>
>>>Please download, test, and try it out:
>>>
>>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>
>>>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:
>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>
>> It is tagged from this branch:
>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>
>>
>>>
>> Should we release this? Vote closes on Feb 8th.
>>
>>>
>>>Regards,
>>>Mohammad
>>
>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
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?
Regards,
Mohammad
----- Original Message -----
From: Chris Douglas <cd...@apache.org>
To: oozie-dev@incubator.apache.org
Cc: oozie-users@incubator.apache.org; Mohammad Islam <mi...@yahoo.com>; bigtop-dev@incubator.apache.org
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 <rv...@apache.org> 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
file:
----
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:
http://incubator.apache.org/oozie
----
> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>
>>>Please download, test, and try it out:
>>>
>>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>
>>>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:
>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>
>> It is tagged from this branch:
>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>
>>
>>>
>> Should we release this? Vote closes on Feb 8th.
>>
>>>
>>>Regards,
>>>Mohammad
>>
>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Chris Douglas <cd...@apache.org>.
On Mon, Feb 6, 2012 at 8:51 AM, Roman Shaposhnik <rv...@apache.org> 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
file:
----
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:
http://incubator.apache.org/oozie
----
> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>
>>>Please download, test, and try it out:
>>>
>>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>
>>>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:
>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>
>> It is tagged from this branch:
>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>
>>
>>>
>> Should we release this? Vote closes on Feb 8th.
>>
>>>
>>>Regards,
>>>Mohammad
>>
>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
>> >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.
>>
>> This one is not clear to me.
>> What is the error message and how did you get that?
>All the details are on this JIRA:
>https://issues.apache.org/jira/browse/OOZIE-680
>I strongly suggest that this gets fixed, since it makes it difficult to
>untar your tarball on certain versions of tar.
Didn't look into the JIRA previously.
Got the issue.
Regards,
Mohammad
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
>> >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.
>>
>> This one is not clear to me.
>> What is the error message and how did you get that?
>All the details are on this JIRA:
>https://issues.apache.org/jira/browse/OOZIE-680
>I strongly suggest that this gets fixed, since it makes it difficult to
>untar your tarball on certain versions of tar.
Didn't look into the JIRA previously.
Got the issue.
Regards,
Mohammad
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
>> >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.
>>
>> This one is not clear to me.
>> What is the error message and how did you get that?
>All the details are on this JIRA:
>https://issues.apache.org/jira/browse/OOZIE-680
>I strongly suggest that this gets fixed, since it makes it difficult to
>untar your tarball on certain versions of tar.
Didn't look into the JIRA previously.
Got the issue.
Regards,
Mohammad
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Feb 6, 2012 at 3:02 PM, Mohammad Islam <mi...@yahoo.com> wrote:
> This version of oozie is not for hadoop 0.23. It will come to the next release..
Understood, but we have local Bigtop patches in that branch that make it better
for hadoop-0.23.
>>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.
>
> I was following the HowToRelease instructions from HCatalog which doesn't said it.
> I had a chat with Alejandro on this last week. We thought we would include it in the next release.
> Now I think we should do it in this release too.
I don't think including source code is optional when doing an Apache release.
> >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.
>
> This one is not clear to me.
> What is the error message and how did you get that?
All the details are on this JIRA:
https://issues.apache.org/jira/browse/OOZIE-680
I strongly suggest that this gets fixed, since it makes it difficult to
untar your tarball on certain versions of tar.
Thanks,
Roman.
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Feb 6, 2012 at 3:02 PM, Mohammad Islam <mi...@yahoo.com> wrote:
> This version of oozie is not for hadoop 0.23. It will come to the next release..
Understood, but we have local Bigtop patches in that branch that make it better
for hadoop-0.23.
>>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.
>
> I was following the HowToRelease instructions from HCatalog which doesn't said it.
> I had a chat with Alejandro on this last week. We thought we would include it in the next release.
> Now I think we should do it in this release too.
I don't think including source code is optional when doing an Apache release.
> >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.
>
> This one is not clear to me.
> What is the error message and how did you get that?
All the details are on this JIRA:
https://issues.apache.org/jira/browse/OOZIE-680
I strongly suggest that this gets fixed, since it makes it difficult to
untar your tarball on certain versions of tar.
Thanks,
Roman.
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Feb 6, 2012 at 3:02 PM, Mohammad Islam <mi...@yahoo.com> wrote:
> This version of oozie is not for hadoop 0.23. It will come to the next release..
Understood, but we have local Bigtop patches in that branch that make it better
for hadoop-0.23.
>>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.
>
> I was following the HowToRelease instructions from HCatalog which doesn't said it.
> I had a chat with Alejandro on this last week. We thought we would include it in the next release.
> Now I think we should do it in this release too.
I don't think including source code is optional when doing an Apache release.
> >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.
>
> This one is not clear to me.
> What is the error message and how did you get that?
All the details are on this JIRA:
https://issues.apache.org/jira/browse/OOZIE-680
I strongly suggest that this gets fixed, since it makes it difficult to
untar your tarball on certain versions of tar.
Thanks,
Roman.
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Hi Roman,
Thanks for your feedbacks.
>I pulled the RC into Bigtop (both branches: trunk [based on Hadoop 1.0]
and hadoop-0.23) and noticed a couple of issues:
This version of oozie is not for hadoop 0.23. It will come to the next release..
>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.
I was following the HowToRelease instructions from HCatalog which doesn't said it.
I had a chat with Alejandro on this last week. We thought we would include it in the next release.
Now I think we should do it in this release too.
> 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.
Will do that.
>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.
This one is not clear to me.
What is the error message and how did you get that?
Regards,
Mohammad
>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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
> It is tagged from this branch:
> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
> Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Hi Roman,
Thanks for your feedbacks.
>I pulled the RC into Bigtop (both branches: trunk [based on Hadoop 1.0]
and hadoop-0.23) and noticed a couple of issues:
This version of oozie is not for hadoop 0.23. It will come to the next release..
>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.
I was following the HowToRelease instructions from HCatalog which doesn't said it.
I had a chat with Alejandro on this last week. We thought we would include it in the next release.
Now I think we should do it in this release too.
> 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.
Will do that.
>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.
This one is not clear to me.
What is the error message and how did you get that?
Regards,
Mohammad
>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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
> It is tagged from this branch:
> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
> Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Chris Douglas <cd...@apache.org>.
On Mon, Feb 6, 2012 at 8:51 AM, Roman Shaposhnik <rv...@apache.org> 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
file:
----
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:
http://incubator.apache.org/oozie
----
> 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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>>
>>>Please download, test, and try it out:
>>>
>>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>>
>>>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:
>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>>
>> It is tagged from this branch:
>> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>>
>>
>>>
>> Should we release this? Vote closes on Feb 8th.
>>
>>>
>>>Regards,
>>>Mohammad
>>
>>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Feb 6, 2012 at 8:51 AM, Roman Shaposhnik <rv...@apache.org> wrote:
> 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.
https://issues.apache.org/jira/browse/OOZIE-680 now has a patch attached to it.
Thanks,
Roman.
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Hi Roman,
Thanks for your feedbacks.
>I pulled the RC into Bigtop (both branches: trunk [based on Hadoop 1.0]
and hadoop-0.23) and noticed a couple of issues:
This version of oozie is not for hadoop 0.23. It will come to the next release..
>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.
I was following the HowToRelease instructions from HCatalog which doesn't said it.
I had a chat with Alejandro on this last week. We thought we would include it in the next release.
Now I think we should do it in this release too.
> 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.
Will do that.
>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.
This one is not clear to me.
What is the error message and how did you get that?
Regards,
Mohammad
>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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
> It is tagged from this branch:
> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
> Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Roman Shaposhnik <rv...@apache.org>.
Hi Mohammad,
I pulled the RC into Bigtop (both branches: trunk [based on Hadoop 1.0]
and hadoop-0.23) and noticed a couple of issues:
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.
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.
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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
> It is tagged from this branch:
> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
> Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Roman Shaposhnik <rv...@apache.org>.
Hi Mohammad,
I pulled the RC into Bigtop (both branches: trunk [based on Hadoop 1.0]
and hadoop-0.23) and noticed a couple of issues:
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.
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.
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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
> It is tagged from this branch:
> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
> Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Alan Gates <ga...@hortonworks.com>.
My bad, I thought I checked both links, but apparently not. I'll try this one out, with the proper link this time.
Alan.
On Feb 6, 2012, at 12:54 PM, Mohammad Islam wrote:
> Hi Alan,
> Thanks for your comment.
>
> We indeed created a tar file and the link is in that email.
>
> http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>
>
> Also we followed the steps given in HCatalog.
>
> Most of the comments by others are to include the src code which is missing in HCatalog.
>
> Regards,
> Mohammad
>
>
>
>
> ----- Original Message -----
> From: Alan Gates <ga...@hortonworks.com>
> To: oozie-users@incubator.apache.org
> Cc:
> Sent: Monday, February 6, 2012 12:24 PM
> Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
>
> -1.
>
> Generally to call a release vote, there needs to be a specific set of bits to vote on. The proposed tag looks fine, but before you call a vote this should be wrapped into a tar, zip, or whatever and proposed as a release. This tar file should contain all the files tagged in SVN with this release-3.1.3-rc0 tag.
>
> For notes on how to go through this process, see https://cwiki.apache.org/confluence/display/HCATALOG/HowToRelease This won't work exactly for you since the tools are different (ant and forrest instead of maven), but it should hit the highlights of what is necessary.
>
> Alan.
>
> On Feb 6, 2012, at 1:05 AM, Mohammad Islam wrote:
>
>> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Hi Alan,
Thanks for your comment.
We indeed created a tar file and the link is in that email.
http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
Also we followed the steps given in HCatalog.
Most of the comments by others are to include the src code which is missing in HCatalog.
Regards,
Mohammad
----- Original Message -----
From: Alan Gates <ga...@hortonworks.com>
To: oozie-users@incubator.apache.org
Cc:
Sent: Monday, February 6, 2012 12:24 PM
Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
-1.
Generally to call a release vote, there needs to be a specific set of bits to vote on. The proposed tag looks fine, but before you call a vote this should be wrapped into a tar, zip, or whatever and proposed as a release. This tar file should contain all the files tagged in SVN with this release-3.1.3-rc0 tag.
For notes on how to go through this process, see https://cwiki.apache.org/confluence/display/HCATALOG/HowToRelease This won't work exactly for you since the tools are different (ant and forrest instead of maven), but it should hit the highlights of what is necessary.
Alan.
On Feb 6, 2012, at 1:05 AM, Mohammad Islam wrote:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Alan Gates <ga...@hortonworks.com>.
-1.
Generally to call a release vote, there needs to be a specific set of bits to vote on. The proposed tag looks fine, but before you call a vote this should be wrapped into a tar, zip, or whatever and proposed as a release. This tar file should contain all the files tagged in SVN with this release-3.1.3-rc0 tag.
For notes on how to go through this process, see https://cwiki.apache.org/confluence/display/HCATALOG/HowToRelease This won't work exactly for you since the tools are different (ant and forrest instead of maven), but it should hit the highlights of what is necessary.
Alan.
On Feb 6, 2012, at 1:05 AM, Mohammad Islam wrote:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Alan Gates <ga...@hortonworks.com>.
On Feb 6, 2012, at 11:40 PM, Mohammad Islam wrote:
>
>> The NOTICE file looks good. The LICENSE file looks good except that I cannot map which included files have which license. According >to http://incubator.apache.org/guides/releasemanagement.html this is to be included in the LICENSE file with each LICENSE. It would be better if both files were at >the top level in the distribution instead of inside oozie-server.
>
>
> We will look into more explained LICENSE file. Do you think it is must for this release?
No, I wouldn't have voted -1 on this issue alone. But the sooner it's fixed the better.
Alan.
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Thanks again Alan for valuable comments.
>-1.
>The readme.txt in the top directory is clearly a hold over from the Yahoo days. It needs updated or removed. Oozie should be referred to as "Apache Oozie", not >"Yahoo's workflow engine". Yahoo's disclaimer of support should be removed, as this is no longer being released by Yahoo. Are docs still only available >yahoo.github.com and not from incubator.apache.org/oozie? Finally the email address for questions should be oozie-users@incubator.apache.org not >@yahoogroups.com.
Devaraj also made the same comments. We already took care of this. http://issues.apache.org/jira/browse/OOZIE-681.
>You need to add a DISCLAIMER file, see http://incubator.apache.org/guides/releasemanagement.html (search on disclaimer) for details. You can find an example >in HCatalog's source. This file should be at the top level in the distribution.
Also taken care of. http://issues.apache.org/jira/browse/OOZIE-683
>The NOTICE file looks good. The LICENSE file looks good except that I cannot map which included files have which license. According >to http://incubator.apache.org/guides/releasemanagement.html this is to be included in the LICENSE file with each LICENSE. It would be better if both files were at >the top level in the distribution instead of inside oozie-server.
We will look into more explained LICENSE file. Do you think it is must for this release?
>(As a general question here, why does the distribution include so many Tomcat plugins? I checked and most if not all of these are available via maven, which the >build already uses. This does not need to be changed or fixed before the release (or ever I guess), but I was just curious.)
I believe those were added because we include a built-in tomcat server with oozie package. So that user can quickly/easily install oozie with less extra downloads.
>Why are the release notes from Tomcat included in the oozie-server directory? This is confusing. If you feel they add value for the user you might want to rename >them TOMCAT-RELEASE-NOTES or something so users understand what they are. Same comment for the RUNNING file. Neither of these are show stoppers for >the release.
We will look into that.
>The rat-report looks beautiful.
>Signature and md5 check out.
>Sorry to be so nitpicky, but if we get this right now it will avoid getting hammered when you take the vote to general@.
Not at all. We indeed appreciate this help. This is our first release. We expect to learn a lot of the process during this release that would make our future release easier.
Also , as you mentioned, before sending to general, we could catch as much potential issues as possible.
Regards,
Mohammad
>Alan.
On 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>> Please download, test, and try it out:
>>
>> http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>> 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:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
> It is tagged from this branch:
> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
> Should we release this? Vote closes on Feb 8th.
>
>>
>> Regards,
>> Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Alan Gates <ga...@hortonworks.com>.
-1.
The readme.txt in the top directory is clearly a hold over from the Yahoo days. It needs updated or removed. Oozie should be referred to as "Apache Oozie", not "Yahoo's workflow engine". Yahoo's disclaimer of support should be removed, as this is no longer being released by Yahoo. Are docs still only available at yahoo.github.com and not from incubator.apache.org/oozie? Finally the email address for questions should be oozie-users@incubator.apache.org not @yahoogroups.com.
You need to add a DISCLAIMER file, see http://incubator.apache.org/guides/releasemanagement.html (search on disclaimer) for details. You can find an example in HCatalog's source. This file should be at the top level in the distribution.
The NOTICE file looks good. The LICENSE file looks good except that I cannot map which included files have which license. According to http://incubator.apache.org/guides/releasemanagement.html this is to be included in the LICENSE file with each LICENSE. It would be better if both files were at the top level in the distribution instead of inside oozie-server.
(As a general question here, why does the distribution include so many Tomcat plugins? I checked and most if not all of these are available via maven, which the build already uses. This does not need to be changed or fixed before the release (or ever I guess), but I was just curious.)
Why are the release notes from Tomcat included in the oozie-server directory? This is confusing. If you feel they add value for the user you might want to rename them TOMCAT-RELEASE-NOTES or something so users understand what they are. Same comment for the RUNNING file. Neither of these are show stoppers for the release.
The rat-report looks beautiful.
Signature and md5 check out.
Sorry to be so nitpicky, but if we get this right now it will avoid getting hammered when you take the vote to general@.
Alan.
On 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>> Please download, test, and try it out:
>>
>> http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>> 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:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
> It is tagged from this branch:
> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
> Should we release this? Vote closes on Feb 8th.
>
>>
>> Regards,
>> Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Roman Shaposhnik <rv...@apache.org>.
Hi Mohammad,
I pulled the RC into Bigtop (both branches: trunk [based on Hadoop 1.0]
and hadoop-0.23) and noticed a couple of issues:
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.
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.
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 <mi...@yahoo.com> 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 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
> http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
> It is tagged from this branch:
> http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
> Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Thanks Thiruvel.
It appears your build succeeds but in two test cases you see errors.
We are looking into that.
Regards,
Mohammad
----- Original Message -----
From: Thiruvel Thirumoolan <th...@yahoo-inc.com>
To: "oozie-users@incubator.apache.org" <oo...@incubator.apache.org>; Mohammad Islam <mi...@yahoo.com>; oozie-dev <oo...@incubator.apache.org>
Cc:
Sent: Monday, February 6, 2012 7:38 AM
Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Downloaded the sources and ran mkdistro.sh. 2 tests fail, are these known
issues? Or could there be something wrong with my setup.
<log>
Running org.apache.oozie.command.coord.TestCoordChangeXCommand
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.687 sec
<<< FAILURE!
...
...
Results :
Tests in error:
testCoordChangeXCommand(org.apache.oozie.command.coord.TestCoordChangeXComm
and)
testCoordChangeEndTime(org.apache.oozie.command.coord.TestCoordChangeXComma
nd)
Tests run: 709, Failures: 0, Errors: 2, Skipped: 0
<log>
Environment:
RHEL 5.7
Maven 3.0.3
Java 1.6
I was able to use the distro generated, run oozie-setup.sh on a node with
Hadoop 20.205 and was able to submit a workflow with Java and Decision
actions and it ran to completion. I have used the embedded derby database
and not tried with MySQL.
Regards,
Thiruvel
On 2/6/12 2:35 PM, "Mohammad Islam" <mi...@yahoo.com> 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
>>http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
>http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
>It is tagged from this branch:
>http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
>Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Mohammad Islam <mi...@yahoo.com>.
Thanks Thiruvel.
It appears your build succeeds but in two test cases you see errors.
We are looking into that.
Regards,
Mohammad
----- Original Message -----
From: Thiruvel Thirumoolan <th...@yahoo-inc.com>
To: "oozie-users@incubator.apache.org" <oo...@incubator.apache.org>; Mohammad Islam <mi...@yahoo.com>; oozie-dev <oo...@incubator.apache.org>
Cc:
Sent: Monday, February 6, 2012 7:38 AM
Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Downloaded the sources and ran mkdistro.sh. 2 tests fail, are these known
issues? Or could there be something wrong with my setup.
<log>
Running org.apache.oozie.command.coord.TestCoordChangeXCommand
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.687 sec
<<< FAILURE!
...
...
Results :
Tests in error:
testCoordChangeXCommand(org.apache.oozie.command.coord.TestCoordChangeXComm
and)
testCoordChangeEndTime(org.apache.oozie.command.coord.TestCoordChangeXComma
nd)
Tests run: 709, Failures: 0, Errors: 2, Skipped: 0
<log>
Environment:
RHEL 5.7
Maven 3.0.3
Java 1.6
I was able to use the distro generated, run oozie-setup.sh on a node with
Hadoop 20.205 and was able to submit a workflow with Java and Decision
actions and it ran to completion. I have used the embedded derby database
and not tried with MySQL.
Regards,
Thiruvel
On 2/6/12 2:35 PM, "Mohammad Islam" <mi...@yahoo.com> 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
>>http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
>http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
>It is tagged from this branch:
>http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
>Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Thiruvel Thirumoolan <th...@yahoo-inc.com>.
Downloaded the sources and ran mkdistro.sh. 2 tests fail, are these known
issues? Or could there be something wrong with my setup.
<log>
Running org.apache.oozie.command.coord.TestCoordChangeXCommand
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.687 sec
<<< FAILURE!
...
...
Results :
Tests in error:
testCoordChangeXCommand(org.apache.oozie.command.coord.TestCoordChangeXComm
and)
testCoordChangeEndTime(org.apache.oozie.command.coord.TestCoordChangeXComma
nd)
Tests run: 709, Failures: 0, Errors: 2, Skipped: 0
<log>
Environment:
RHEL 5.7
Maven 3.0.3
Java 1.6
I was able to use the distro generated, run oozie-setup.sh on a node with
Hadoop 20.205 and was able to submit a workflow with Java and Decision
actions and it ran to completion. I have used the embedded derby database
and not tried with MySQL.
Regards,
Thiruvel
On 2/6/12 2:35 PM, "Mohammad Islam" <mi...@yahoo.com> 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
>>http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
>http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
>It is tagged from this branch:
>http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
>Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>
Re: [VOTE] Release Oozie 3.1.3 (candidate 0)
Posted by Thiruvel Thirumoolan <th...@yahoo-inc.com>.
Downloaded the sources and ran mkdistro.sh. 2 tests fail, are these known
issues? Or could there be something wrong with my setup.
<log>
Running org.apache.oozie.command.coord.TestCoordChangeXCommand
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.687 sec
<<< FAILURE!
...
...
Results :
Tests in error:
testCoordChangeXCommand(org.apache.oozie.command.coord.TestCoordChangeXComm
and)
testCoordChangeEndTime(org.apache.oozie.command.coord.TestCoordChangeXComma
nd)
Tests run: 709, Failures: 0, Errors: 2, Skipped: 0
<log>
Environment:
RHEL 5.7
Maven 3.0.3
Java 1.6
I was able to use the distro generated, run oozie-setup.sh on a node with
Hadoop 20.205 and was able to submit a workflow with Java and Decision
actions and it ran to completion. I have used the embedded derby database
and not tried with MySQL.
Regards,
Thiruvel
On 2/6/12 2:35 PM, "Mohammad Islam" <mi...@yahoo.com> 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
>>http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
>>
>>Please download, test, and try it out:
>>
>>http://people.apache.org/~kamrul/oozie-3.1.3-candidate-0/
>>
>>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:
>http://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc0/
>>
>It is tagged from this branch:
>http://svn.apache.org/repos/asf/incubator/oozie/branches/branch-3.1/
>>
>
>>
>Should we release this? Vote closes on Feb 8th.
>
>>
>>Regards,
>>Mohammad
>
>>