You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by Virag Kothari <vi...@yahoo-inc.com> on 2013/01/18 00:50:00 UTC
[VOTE] Release Oozie 3.3.1 (candidate 1)
Hi,
The release candidate 1 for Oozie 3.3.1 is available.
Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from 3.2 to 3.3. In addition, it has several other improvements for stability and few bug fixes.
Detail release log can be found at http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
Keys to verify the signature of the release artifact are available at
http://www.apache.org/dist/oozie/KEYS
Please download, test, and try it out:
http://people.apache.org/~virag/oozie-3.3.1-rc1/<http://people.apache.org/~virag/oozie-3.3.1-rc0/>
The release, md5 signature, gpg signature, and rat report can all
be found at the above address.
Vote closes after 3 days from now. (Jan 20 16:00 PST)
Thanks,
Virag
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Virag Kothari <vi...@yahoo-inc.com>.
Good observation, Harsh. I also think we should get rid of builds and
build-setup.
I am not sure whether work.log is relevant or not now.
Regards,
Virag
On 1/21/13 2:20 AM, "Harsh J" <ha...@cloudera.com> wrote:
>+1, I downloaded, built and ran the test suite.
>
>Not blockers in any way, but something we could do for the next release
>source build is to get rid of oozie-3.3.1/build-setup/
>and oozie-3.3.1/builds/ directories as they are apparently not useful for
>users. The former seems empty completely, although it retains a package
>structure?
>
>Also, perhaps we can merge work.log into release-notes.txt, if its still
>relevant?
>
>
>On Sat, Jan 19, 2013 at 7:08 AM, Ryota Egashira
><eg...@yahoo-inc.com>wrote:
>
>> Thanks Virag.
>>
>> Verified md5, checked release-log, built and ran on Hadoop 1.1.1 and
>> tested workflow/coord/bundle examples.
>>
>> +1
>>
>> Ryota
>>
>> On 1/18/13 11:07 AM, "Mona Chitnis" <ch...@yahoo-inc.com> wrote:
>>
>> >+1
>> >Verified md5 and signature, built distro and started successfully with
>> >Hadoop 1.1.1. Ran a few examples.
>> >Release log looks fine.
>> >
>> >--
>> >Mona
>> >
>> >On 1/17/13 6:15 PM, "Robert Kanter" <rk...@cloudera.com> wrote:
>> >
>> >>+ I verified the md5
>> >>
>> >>+ release-log.txt no longer says "unreleased"
>> >>
>> >>+ I ran the tests successfully
>> >>
>> >>+ Built and started correctly against hadoop 1.1.1
>> >>
>> >>+ Submitted some of the example jobs, played with the web UI and CLI a
>> >>bit
>> >>
>> >>
>> >>+1
>> >>
>> >>
>> >>thanks
>> >>- Robert
>> >>
>> >>On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur
>> >><tu...@cloudera.com>wrote:
>> >>
>> >>> +1
>> >>>
>> >>> verified MD5 and signature.
>> >>> removed release-log.txt file from rc0 and rc1 and run "find . -type
>>f |
>> >>> sort | xargs -I % cat | md5" in both, got same MD5 in both (so
>>build,
>> >>> install, config, run checks apply)
>> >>>
>> >>>
>> >>> On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com>
>> >>> wrote:
>> >>>
>> >>> > Hi,
>> >>> >
>> >>> > The release candidate 1 for Oozie 3.3.1 is available.
>> >>> >
>> >>> > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from
>> >>>3.2 to
>> >>> > 3.3. In addition, it has several other improvements for stability
>>and
>> >>>few
>> >>> > bug fixes.
>> >>> > Detail release log can be found at
>> >>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
>> >>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
>> >>> >
>> >>> >
>> >>> > Keys to verify the signature of the release artifact are
>>available at
>> >>> >
>> >>> > http://www.apache.org/dist/oozie/KEYS
>> >>> >
>> >>> >
>> >>> > Please download, test, and try it out:
>> >>> >
>> >>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/<
>> >>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/>
>> >>> >
>> >>> >
>> >>> > The release, md5 signature, gpg signature, and rat report can all
>> >>> > be found at the above address.
>> >>> >
>> >>> >
>> >>> > Vote closes after 3 days from now. (Jan 20 16:00 PST)
>> >>> >
>> >>> >
>> >>> > Thanks,
>> >>> >
>> >>> > Virag
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Alejandro
>> >>>
>> >
>>
>>
>
>
>--
>Harsh J
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Harsh J <ha...@cloudera.com>.
+1, I downloaded, built and ran the test suite.
Not blockers in any way, but something we could do for the next release
source build is to get rid of oozie-3.3.1/build-setup/
and oozie-3.3.1/builds/ directories as they are apparently not useful for
users. The former seems empty completely, although it retains a package
structure?
Also, perhaps we can merge work.log into release-notes.txt, if its still
relevant?
On Sat, Jan 19, 2013 at 7:08 AM, Ryota Egashira <eg...@yahoo-inc.com>wrote:
> Thanks Virag.
>
> Verified md5, checked release-log, built and ran on Hadoop 1.1.1 and
> tested workflow/coord/bundle examples.
>
> +1
>
> Ryota
>
> On 1/18/13 11:07 AM, "Mona Chitnis" <ch...@yahoo-inc.com> wrote:
>
> >+1
> >Verified md5 and signature, built distro and started successfully with
> >Hadoop 1.1.1. Ran a few examples.
> >Release log looks fine.
> >
> >--
> >Mona
> >
> >On 1/17/13 6:15 PM, "Robert Kanter" <rk...@cloudera.com> wrote:
> >
> >>+ I verified the md5
> >>
> >>+ release-log.txt no longer says "unreleased"
> >>
> >>+ I ran the tests successfully
> >>
> >>+ Built and started correctly against hadoop 1.1.1
> >>
> >>+ Submitted some of the example jobs, played with the web UI and CLI a
> >>bit
> >>
> >>
> >>+1
> >>
> >>
> >>thanks
> >>- Robert
> >>
> >>On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur
> >><tu...@cloudera.com>wrote:
> >>
> >>> +1
> >>>
> >>> verified MD5 and signature.
> >>> removed release-log.txt file from rc0 and rc1 and run "find . -type f |
> >>> sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
> >>> install, config, run checks apply)
> >>>
> >>>
> >>> On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com>
> >>> wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > The release candidate 1 for Oozie 3.3.1 is available.
> >>> >
> >>> > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from
> >>>3.2 to
> >>> > 3.3. In addition, it has several other improvements for stability and
> >>>few
> >>> > bug fixes.
> >>> > Detail release log can be found at
> >>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
> >>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
> >>> >
> >>> >
> >>> > Keys to verify the signature of the release artifact are available at
> >>> >
> >>> > http://www.apache.org/dist/oozie/KEYS
> >>> >
> >>> >
> >>> > Please download, test, and try it out:
> >>> >
> >>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/<
> >>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/>
> >>> >
> >>> >
> >>> > The release, md5 signature, gpg signature, and rat report can all
> >>> > be found at the above address.
> >>> >
> >>> >
> >>> > Vote closes after 3 days from now. (Jan 20 16:00 PST)
> >>> >
> >>> >
> >>> > Thanks,
> >>> >
> >>> > Virag
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Alejandro
> >>>
> >
>
>
--
Harsh J
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Ryota Egashira <eg...@yahoo-inc.com>.
Thanks Virag.
Verified md5, checked release-log, built and ran on Hadoop 1.1.1 and
tested workflow/coord/bundle examples.
+1
Ryota
On 1/18/13 11:07 AM, "Mona Chitnis" <ch...@yahoo-inc.com> wrote:
>+1
>Verified md5 and signature, built distro and started successfully with
>Hadoop 1.1.1. Ran a few examples.
>Release log looks fine.
>
>--
>Mona
>
>On 1/17/13 6:15 PM, "Robert Kanter" <rk...@cloudera.com> wrote:
>
>>+ I verified the md5
>>
>>+ release-log.txt no longer says "unreleased"
>>
>>+ I ran the tests successfully
>>
>>+ Built and started correctly against hadoop 1.1.1
>>
>>+ Submitted some of the example jobs, played with the web UI and CLI a
>>bit
>>
>>
>>+1
>>
>>
>>thanks
>>- Robert
>>
>>On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur
>><tu...@cloudera.com>wrote:
>>
>>> +1
>>>
>>> verified MD5 and signature.
>>> removed release-log.txt file from rc0 and rc1 and run "find . -type f |
>>> sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
>>> install, config, run checks apply)
>>>
>>>
>>> On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com>
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > The release candidate 1 for Oozie 3.3.1 is available.
>>> >
>>> > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from
>>>3.2 to
>>> > 3.3. In addition, it has several other improvements for stability and
>>>few
>>> > bug fixes.
>>> > Detail release log can be found at
>>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
>>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
>>> >
>>> >
>>> > Keys to verify the signature of the release artifact are available at
>>> >
>>> > http://www.apache.org/dist/oozie/KEYS
>>> >
>>> >
>>> > Please download, test, and try it out:
>>> >
>>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/<
>>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/>
>>> >
>>> >
>>> > The release, md5 signature, gpg signature, and rat report can all
>>> > be found at the above address.
>>> >
>>> >
>>> > Vote closes after 3 days from now. (Jan 20 16:00 PST)
>>> >
>>> >
>>> > Thanks,
>>> >
>>> > Virag
>>> >
>>>
>>>
>>>
>>> --
>>> Alejandro
>>>
>
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Ryota Egashira <eg...@yahoo-inc.com>.
Thanks Virag.
Verified md5, checked release-log, built and ran on Hadoop 1.1.1 and
tested workflow/coord/bundle examples.
+1
Ryota
On 1/18/13 11:07 AM, "Mona Chitnis" <ch...@yahoo-inc.com> wrote:
>+1
>Verified md5 and signature, built distro and started successfully with
>Hadoop 1.1.1. Ran a few examples.
>Release log looks fine.
>
>--
>Mona
>
>On 1/17/13 6:15 PM, "Robert Kanter" <rk...@cloudera.com> wrote:
>
>>+ I verified the md5
>>
>>+ release-log.txt no longer says "unreleased"
>>
>>+ I ran the tests successfully
>>
>>+ Built and started correctly against hadoop 1.1.1
>>
>>+ Submitted some of the example jobs, played with the web UI and CLI a
>>bit
>>
>>
>>+1
>>
>>
>>thanks
>>- Robert
>>
>>On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur
>><tu...@cloudera.com>wrote:
>>
>>> +1
>>>
>>> verified MD5 and signature.
>>> removed release-log.txt file from rc0 and rc1 and run "find . -type f |
>>> sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
>>> install, config, run checks apply)
>>>
>>>
>>> On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com>
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > The release candidate 1 for Oozie 3.3.1 is available.
>>> >
>>> > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from
>>>3.2 to
>>> > 3.3. In addition, it has several other improvements for stability and
>>>few
>>> > bug fixes.
>>> > Detail release log can be found at
>>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
>>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
>>> >
>>> >
>>> > Keys to verify the signature of the release artifact are available at
>>> >
>>> > http://www.apache.org/dist/oozie/KEYS
>>> >
>>> >
>>> > Please download, test, and try it out:
>>> >
>>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/<
>>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/>
>>> >
>>> >
>>> > The release, md5 signature, gpg signature, and rat report can all
>>> > be found at the above address.
>>> >
>>> >
>>> > Vote closes after 3 days from now. (Jan 20 16:00 PST)
>>> >
>>> >
>>> > Thanks,
>>> >
>>> > Virag
>>> >
>>>
>>>
>>>
>>> --
>>> Alejandro
>>>
>
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Mona Chitnis <ch...@yahoo-inc.com>.
+1
Verified md5 and signature, built distro and started successfully with
Hadoop 1.1.1. Ran a few examples.
Release log looks fine.
--
Mona
On 1/17/13 6:15 PM, "Robert Kanter" <rk...@cloudera.com> wrote:
>+ I verified the md5
>
>+ release-log.txt no longer says "unreleased"
>
>+ I ran the tests successfully
>
>+ Built and started correctly against hadoop 1.1.1
>
>+ Submitted some of the example jobs, played with the web UI and CLI a bit
>
>
>+1
>
>
>thanks
>- Robert
>
>On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur
><tu...@cloudera.com>wrote:
>
>> +1
>>
>> verified MD5 and signature.
>> removed release-log.txt file from rc0 and rc1 and run "find . -type f |
>> sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
>> install, config, run checks apply)
>>
>>
>> On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com>
>> wrote:
>>
>> > Hi,
>> >
>> > The release candidate 1 for Oozie 3.3.1 is available.
>> >
>> > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from
>>3.2 to
>> > 3.3. In addition, it has several other improvements for stability and
>>few
>> > bug fixes.
>> > Detail release log can be found at
>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
>> >
>> >
>> > Keys to verify the signature of the release artifact are available at
>> >
>> > http://www.apache.org/dist/oozie/KEYS
>> >
>> >
>> > Please download, test, and try it out:
>> >
>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/<
>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/>
>> >
>> >
>> > The release, md5 signature, gpg signature, and rat report can all
>> > be found at the above address.
>> >
>> >
>> > Vote closes after 3 days from now. (Jan 20 16:00 PST)
>> >
>> >
>> > Thanks,
>> >
>> > Virag
>> >
>>
>>
>>
>> --
>> Alejandro
>>
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Mona Chitnis <ch...@yahoo-inc.com>.
+1
Verified md5 and signature, built distro and started successfully with
Hadoop 1.1.1. Ran a few examples.
Release log looks fine.
--
Mona
On 1/17/13 6:15 PM, "Robert Kanter" <rk...@cloudera.com> wrote:
>+ I verified the md5
>
>+ release-log.txt no longer says "unreleased"
>
>+ I ran the tests successfully
>
>+ Built and started correctly against hadoop 1.1.1
>
>+ Submitted some of the example jobs, played with the web UI and CLI a bit
>
>
>+1
>
>
>thanks
>- Robert
>
>On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur
><tu...@cloudera.com>wrote:
>
>> +1
>>
>> verified MD5 and signature.
>> removed release-log.txt file from rc0 and rc1 and run "find . -type f |
>> sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
>> install, config, run checks apply)
>>
>>
>> On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com>
>> wrote:
>>
>> > Hi,
>> >
>> > The release candidate 1 for Oozie 3.3.1 is available.
>> >
>> > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from
>>3.2 to
>> > 3.3. In addition, it has several other improvements for stability and
>>few
>> > bug fixes.
>> > Detail release log can be found at
>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
>> >
>> >
>> > Keys to verify the signature of the release artifact are available at
>> >
>> > http://www.apache.org/dist/oozie/KEYS
>> >
>> >
>> > Please download, test, and try it out:
>> >
>> > http://people.apache.org/~virag/oozie-3.3.1-rc1/<
>> > http://people.apache.org/~virag/oozie-3.3.1-rc0/>
>> >
>> >
>> > The release, md5 signature, gpg signature, and rat report can all
>> > be found at the above address.
>> >
>> >
>> > Vote closes after 3 days from now. (Jan 20 16:00 PST)
>> >
>> >
>> > Thanks,
>> >
>> > Virag
>> >
>>
>>
>>
>> --
>> Alejandro
>>
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Robert Kanter <rk...@cloudera.com>.
+ I verified the md5
+ release-log.txt no longer says "unreleased"
+ I ran the tests successfully
+ Built and started correctly against hadoop 1.1.1
+ Submitted some of the example jobs, played with the web UI and CLI a bit
+1
thanks
- Robert
On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur <tu...@cloudera.com>wrote:
> +1
>
> verified MD5 and signature.
> removed release-log.txt file from rc0 and rc1 and run "find . -type f |
> sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
> install, config, run checks apply)
>
>
> On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com>
> wrote:
>
> > Hi,
> >
> > The release candidate 1 for Oozie 3.3.1 is available.
> >
> > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from 3.2 to
> > 3.3. In addition, it has several other improvements for stability and few
> > bug fixes.
> > Detail release log can be found at
> > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
> > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
> >
> >
> > Keys to verify the signature of the release artifact are available at
> >
> > http://www.apache.org/dist/oozie/KEYS
> >
> >
> > Please download, test, and try it out:
> >
> > http://people.apache.org/~virag/oozie-3.3.1-rc1/<
> > http://people.apache.org/~virag/oozie-3.3.1-rc0/>
> >
> >
> > The release, md5 signature, gpg signature, and rat report can all
> > be found at the above address.
> >
> >
> > Vote closes after 3 days from now. (Jan 20 16:00 PST)
> >
> >
> > Thanks,
> >
> > Virag
> >
>
>
>
> --
> Alejandro
>
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Robert Kanter <rk...@cloudera.com>.
+ I verified the md5
+ release-log.txt no longer says "unreleased"
+ I ran the tests successfully
+ Built and started correctly against hadoop 1.1.1
+ Submitted some of the example jobs, played with the web UI and CLI a bit
+1
thanks
- Robert
On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur <tu...@cloudera.com>wrote:
> +1
>
> verified MD5 and signature.
> removed release-log.txt file from rc0 and rc1 and run "find . -type f |
> sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
> install, config, run checks apply)
>
>
> On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com>
> wrote:
>
> > Hi,
> >
> > The release candidate 1 for Oozie 3.3.1 is available.
> >
> > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from 3.2 to
> > 3.3. In addition, it has several other improvements for stability and few
> > bug fixes.
> > Detail release log can be found at
> > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
> > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
> >
> >
> > Keys to verify the signature of the release artifact are available at
> >
> > http://www.apache.org/dist/oozie/KEYS
> >
> >
> > Please download, test, and try it out:
> >
> > http://people.apache.org/~virag/oozie-3.3.1-rc1/<
> > http://people.apache.org/~virag/oozie-3.3.1-rc0/>
> >
> >
> > The release, md5 signature, gpg signature, and rat report can all
> > be found at the above address.
> >
> >
> > Vote closes after 3 days from now. (Jan 20 16:00 PST)
> >
> >
> > Thanks,
> >
> > Virag
> >
>
>
>
> --
> Alejandro
>
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
+1
verified MD5 and signature.
removed release-log.txt file from rc0 and rc1 and run "find . -type f |
sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
install, config, run checks apply)
On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com> wrote:
> Hi,
>
> The release candidate 1 for Oozie 3.3.1 is available.
>
> Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from 3.2 to
> 3.3. In addition, it has several other improvements for stability and few
> bug fixes.
> Detail release log can be found at
> http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
> http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
>
>
> Keys to verify the signature of the release artifact are available at
>
> http://www.apache.org/dist/oozie/KEYS
>
>
> Please download, test, and try it out:
>
> http://people.apache.org/~virag/oozie-3.3.1-rc1/<
> http://people.apache.org/~virag/oozie-3.3.1-rc0/>
>
>
> The release, md5 signature, gpg signature, and rat report can all
> be found at the above address.
>
>
> Vote closes after 3 days from now. (Jan 20 16:00 PST)
>
>
> Thanks,
>
> Virag
>
--
Alejandro
Re: [VOTE] Release Oozie 3.3.1 (candidate 1)
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
+1
verified MD5 and signature.
removed release-log.txt file from rc0 and rc1 and run "find . -type f |
sort | xargs -I % cat | md5" in both, got same MD5 in both (so build,
install, config, run checks apply)
On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <vi...@yahoo-inc.com> wrote:
> Hi,
>
> The release candidate 1 for Oozie 3.3.1 is available.
>
> Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from 3.2 to
> 3.3. In addition, it has several other improvements for stability and few
> bug fixes.
> Detail release log can be found at
> http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt<
> http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt>
>
>
> Keys to verify the signature of the release artifact are available at
>
> http://www.apache.org/dist/oozie/KEYS
>
>
> Please download, test, and try it out:
>
> http://people.apache.org/~virag/oozie-3.3.1-rc1/<
> http://people.apache.org/~virag/oozie-3.3.1-rc0/>
>
>
> The release, md5 signature, gpg signature, and rat report can all
> be found at the above address.
>
>
> Vote closes after 3 days from now. (Jan 20 16:00 PST)
>
>
> Thanks,
>
> Virag
>
--
Alejandro