This is done now. Changed version to 4.0.0 for the following
project = OOZIE AND fixVersion = trunk AND resolution = Fixed AND Key not
in (OOZIE-1453, OOZIE-1447, OOZIE-1440) AND fixVersion not in ("3.3.0",
"3.3.1", "3.3.2")
Also removed trunk from FixVersion/s when there were other versions.
Regards,
Rohini
On Sat, Jul 13, 2013 at 6:40 PM, Rohini Palaniswamy <rohini.adi...@gmail.com
> wrote:
> > Do you mean the "Fix Version" field?
> Yes.
>
> > I know that many JIRAs are using that
> to also mean the "target version", which is a field we don't have
> "Fix Version" is the equivalent of bugzilla "Target Version".
>
> > I'm sure there are some JIRAs marked with
> "Fix Version" as trunk that we don't want in 4.0, right?
> Yes. A couple of jiras went into trunk after the branching. They will
> not be marked 4.0
>
> Regards,
> Rohini
>
>
> On Fri, Jul 12, 2013 at 2:10 PM, Robert Kanter <rkan...@cloudera.com>wrote:
>
>> Do you mean the "Fix Version" field? I know that many JIRAs are using
>> that
>> to also mean the "target version", which is a field we don't have (perhaps
>> we should have that field?). I'm sure there are some JIRAs marked with
>> "Fix Version" as trunk that we don't want in 4.0, right?
>>
>> - Robert
>>
>>
>> On Fri, Jul 12, 2013 at 11:45 AM, Rohini Palaniswamy <
>> rohini.adi...@gmail.com> wrote:
>>
>> > Planning to do a bulk update of the Fixed version of jiras to branch-4.0
>> > tomorrow. Currently they are marked as trunk. Please let know if there
>> are
>> > any objections.
>> >
>> > Regards,
>> > Rohini
>> >
>> > On Fri, Jun 28, 2013 at 10:27 PM, Rohini Palaniswamy <
>> > rohini.adi...@gmail.com> wrote:
>> >
>> > > Created http://svn.apache.org/viewvc/oozie/branches/branch-4.0/.
>> > >
>> > > Patches yet to be done for branch-4.0.
>> > >
>> > > OOZIE-1379 Generate SLA end_miss event only after confirming against
>> > > persistent store
>> > > OOZIE-1249 and OOZIE-1430 Documentation for JMS notifications and SLA
>> > > monitoring
>> > > OOZIE-1405 Fix flakey unit tests
>> > >
>> > > Regards,
>> > > Rohini
>> > >
>> > > On Fri, Jun 28, 2013 at 11:41 AM, Robert Kanter <rkan...@cloudera.com
>> > >wrote:
>> > >
>> > >> Ah, you're right; thanks.
>> > >>
>> > >> I reviewed the patch, but I'd like someone else to also take a look
>> > >> because
>> > >> I'm not a DB expert.
>> > >>
>> > >> - Robert
>> > >>
>> > >>
>> > >> On Fri, Jun 28, 2013 at 11:30 AM, Virag Kothari <vi...@yahoo-inc.com
>> >
>> > >> wrote:
>> > >>
>> > >> > That change is reverted by OOZIE-1436. Can you review
>> > >> > https://reviews.apache.org/r/12164/ and confirm?
>> > >> > We can keep OOZIE-1437 open to deal the problems we will face when
>> > >> having
>> > >> > a 'proper' fix for the clob/varchar issues.
>> > >> >
>> > >> > Thanks,
>> > >> > Virag
>> > >> >
>> > >> > On 6/28/13 11:12 AM, "Robert Kanter" <rkan...@cloudera.com> wrote:
>> > >> >
>> > >> > >I think we need both; OOZIE-1436 reverts the columns back because
>> of
>> > an
>> > >> > >OpenJPA/Oracle issue and OOZIE-1437 is to fix an if statement
>> added
>> > >> into
>> > >> > >our code (see
>> > >> > >
>> > >> >
>> > >>
>> >
>> https://issues.apache.org/jira/browse/OOZIE-1398?focusedCommentId=13694224
>> > >> >
>> > >>
>> >
>> >&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#com
>> > >> > >ment-13694224
>> > >> > >)
>> > >> > >
>> > >> > >thanks
>> > >> > >- Robert
>> > >> > >
>> > >> > >
>> > >> > >On Fri, Jun 28, 2013 at 11:00 AM, Virag Kothari <
>> vi...@yahoo-inc.com
>> > >
>> > >> > >wrote:
>> > >> > >
>> > >> > >> OOZIE-1436 will convert data varchar column back to lob due to
>> some
>> > >> > >>issues
>> > >> > >> seen (In JIRA description) with OpenJPA.
>> > >> > >>
>> > >> > >>
>> > >> > >> Thanks,
>> > >> > >> Virag
>> > >> > >>
>> > >> > >> On 6/28/13 10:55 AM, "Robert Kanter" <rkan...@cloudera.com>
>> wrote:
>> > >> > >>
>> > >> > >> >Can we also get OOZIE-1437 (paramerize size limit of setData in
>> > >> > >> >JsonWorkflowAction based on user's configuration) in
>> branch-4.0?
>> > >> > >>Without
>> > >> > >> >this, the size of </capture-output> is always hardcoded at max
>> of
>> > >> 2k,
>> > >> > >>even
>> > >> > >> >if the user changes it in oozie-site (because of OOZIE-1398).
>> > >> > >> >
>> > >> > >> >thanks
>> > >> > >> >- Robert
>> > >> > >> >
>> > >> > >> >
>> > >> > >> >On Fri, Jun 28, 2013 at 9:21 AM, Rohini Palaniswamy
>> > >> > >> ><rohini.adi...@gmail.com
>> > >> > >> >> wrote:
>> > >> > >> >
>> > >> > >> >> Hi,
>> > >> > >> >> I am planning to branch trunk as branch-4.0 and trash the
>> > >> current
>> > >> > >> >> branch-4.0 today evening. Discussed this with some of the
>> folks
>> > >> > >>during
>> > >> > >> >>the
>> > >> > >> >> summit. This will facilitate releasing HCat integration, JMS
>> > >> > >> >>notifications
>> > >> > >> >> for job and SLA and SLA monitoring as Oozie 4.0 which we are
>> > done
>> > >> > >>with
>> > >> > >> >> functional testing and in the process of stress testing. This
>> > will
>> > >> > >>free
>> > >> > >> >>up
>> > >> > >> >> the trunk for the next release features of HA, cron based
>> > >> > >>scheduling, DB
>> > >> > >> >> clob column removal to move forward.
>> > >> > >> >>
>> > >> > >> >>
>> > >> > >> >> Patches that need to get into branch-4.0 are
>> > >> > >> >>
>> > >> > >> >> OOZIE-1433 ActionCheckX should override XCommand.getKey() to
>> > >> prevent
>> > >> > >> >> duplicates
>> > >> > >> >> OOZIE-1436 Revert SLA_XML and few other varchar columns back
>> to
>> > >> clob
>> > >> > >> >> OOZIE-1427 Update CredentialsModule docs to mention Hive
>> > >> > >> >> OOZIE-1379 Generate SLA end_miss event only after confirming
>> > >> against
>> > >> > >> >> persistent store
>> > >> > >> >> OOZIE-1435 StatusTransitService unnecessarily updates the
>> > >> > >> >>lastModifiedTime
>> > >> > >> >> of jobs which causes MaterializationService to bring same
>> jobs
>> > in
>> > >> > >>memory
>> > >> > >> >> OOZIE-1249 and OOZIE-1430 Documentation for JMS notifications
>> > and
>> > >> SLA
>> > >> > >> >> monitoring
>> > >> > >> >> Subworkflow notifications don't have workflow as parent id
>> > >> > >> >> And any other issues that crop up during the stress testing.
>> > >> > >> >>
>> > >> > >> >> Hoping most of this will get committed today before we
>> > branch.
>> > >> > >>Please
>> > >> > >> >> bring up any other jiras that we need to get into branch-4
>> > before
>> > >> > >>moving
>> > >> > >> >> towards a release. Looking at a timeline of releasing 4.0 in
>> 3
>> > >> weeks.
>> > >> > >> >>
>> > >> > >> >> Regards,
>> > >> > >> >> Rohini
>> > >> > >> >>
>> > >> > >>
>> > >> > >>
>> > >> >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>
