The 4.0.0 release has hadoop version 2.2.0-SNAPSHOT in the pom files.
Since these artifacts are no longer available on the maven repository, I
think we should do a 4.0.1 release ASAP since OOZIE-1551 updates the pom
versions to the released version 2.2.0.

--Mona

On 10/1/13 1:09 PM, "Robert Kanter" <rkan...@cloudera.com> wrote:

>They recently put up the 2.1.1-beta jars in Maven, so I created a patch
>for
>OOZIE-1551.  However, I haven't had a chance to try it yet and there were
>some test failures (mostly Pig action related).  I don't have time to look
>into the failures now, but I uploaded the patch and listed the failed
>tests
>in case anyone else wants to look into it in the meantime.
>
>
>
>
>On Mon, Sep 23, 2013 at 11:03 AM, Alejandro Abdelnur
><t...@cloudera.com>wrote:
>
>> I suggest we wait till Hadoop 2.1.1-beta is out, unless something nasty
>> creeps out it should be out quite soon.
>>
>>
>> On Mon, Sep 23, 2013 at 6:20 PM, Mona Chitnis <chit...@yahoo-inc.com>
>> wrote:
>>
>> > I'd suggest OOZIE-1448, 1513 and 1530 bug fixes go into 4.0.1 since
>>they
>> > contribute towards stability
>> >
>> > On 9/20/13 4:22 PM, "Robert Kanter" <rkan...@cloudera.com> wrote:
>> >
>> > >Thanks Rohini.  I just put OOZIE-1284 into branch-4.0 and trunk.
>> > >
>> > >I also created OOZIE-1551
>> > ><https://issues.apache.org/jira/browse/OOZIE-1551>to change the
>> > >hadoop-2 profile to use 2.1.0-beta.  Is there anything else
>> > >we want to put in 4.0.1 besides these 3 things?
>> > >
>> > >
>> > >thanks
>> > >- Robert
>> > >
>> > >
>> > >On Fri, Sep 20, 2013 at 1:21 PM, Rohini Palaniswamy
>> > ><rohini.adi...@gmail.com
>> > >> wrote:
>> > >
>> > >> Thanks Robert. Created 4.0.1 branch. OOZIE-1549 is checked in as
>>part
>> of
>> > >> 4.0.1 in branch-4.0. Please go ahead and check in OOZIE-1284 in
>> > >>branch-4.0.
>> > >>
>> > >> Regards,
>> > >> Rohini
>> > >>
>> > >>
>> > >> On Fri, Sep 20, 2013 at 10:05 AM, Robert Kanter
>><rkan...@cloudera.com
>> > >> >wrote:
>> > >>
>> > >> > I guess we need to update the release-log.txt to have a 4.0.1
>> section
>> > >>in
>> > >> > trunk and branch-4.0, but I don't think we need to do anything
>>else.
>> > >> >
>> > >> > And for 4.0.1, according to
>> > >> > https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release,
>> we
>> > >> just
>> > >> > keep using branch-4.0 so no need to create a new branch either.
>> > >> >
>> > >> > Also, I think we should put
>> > >> > OOZIE-1284<https://issues.apache.org/jira/browse/OOZIE-1284
>> > >> > >(oozie.service.SchemaService.wf.ext.schemas
>> > >> > in oozie-site is missing some
>> > >> > newer xsd files) in 4.0.1.
>> > >> >
>> > >> > thanks
>> > >> > - Robert
>> > >> >
>> > >> >
>> > >> > On Fri, Sep 20, 2013 at 9:44 AM, Rohini Palaniswamy <
>> > >> > rohini.adi...@gmail.com
>> > >> > > wrote:
>> > >> >
>> > >> > > I will create a 4.0.1 version in jira for this. Is there
>>anything
>> > >> > > additional that needs to be done than adding the version in
>> Versions
>> > >> tab?
>> > >> > >
>> > >> > > Regards,
>> > >> > > Rohini
>> > >> > >
>> > >> > >
>> > >> > > On Wed, Sep 4, 2013 at 11:27 AM, Robert Kanter
>> > >><rkan...@cloudera.com>
>> > >> > > wrote:
>> > >> > >
>> > >> > > > That's a good idea; we can replace the unreleased
>>2.2.0-SNAPSHOT
>> > >>with
>> > >> > > > 2.1.0-beta for the "hadoop-2" profile.  Is there anything
>>else
>> > >>that
>> > >> > would
>> > >> > > > be good (probably only critical or very minor things) to
>>include
>> > >>in
>> > >> > this
>> > >> > > > release?
>> > >> > > >
>> > >> > > > thanks
>> > >> > > > - Robert
>> > >> > > >
>> > >> > > >
>> > >> > > > On Wed, Sep 4, 2013 at 4:30 AM, Alejandro Abdelnur <
>> > >> t...@cloudera.com
>> > >> > > > >wrote:
>> > >> > > >
>> > >> > > > > I think we should do a new Oozie release using Hadoop
>> > >>2.1.0-beta,
>> > >> > this
>> > >> > > > will
>> > >> > > > > help users and developers to start playing with Hadoop 2 .
>> > >> > > > >
>> > >> > > > > thx.
>> > >> > > > >
>> > >> > > > > --
>> > >> > > > > Alejandro
>> > >> > > > >
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>> >
>>
>>
>> --
>> Alejandro
>>

Reply via email to