Cool - knowing the release process is in motion is a good start. After posting my question I looked back and saw some of the discussion in that direction on the dev mailing list. Bowen - if you have any sort of estimate for how long the release process might take feel free to post it but I won't hold you to it.
On Tue, Jul 22, 2014 at 1:21 AM, Shwetha GS <[email protected]> wrote: > Bowen is driving the release and he has already cut a branch. He can give > the timeline > > > On Mon, Jul 21, 2014 at 7:54 PM, Ben Roling <[email protected]> wrote: > > > Thanks for the link. The JIRA description is obvious enough -- not sure > > how I missed it with my queries. I think this feature will be a nice > > addition. Is there any sort of target release date for 4.1? > > > > > > On Sat, Jul 19, 2014 at 9:10 AM, Shwetha GS <[email protected]> > wrote: > > > > > https://issues.apache.org/jira/browse/OOZIE-1769 adds coordinator > update > > > feature and the jira has the details. This will be part of 4.1 release > > > > > > > > > On Fri, Jul 18, 2014 at 8:35 PM, Ben Roling <[email protected]> > > wrote: > > > > > > > I stumbled upon a post in June linking to slides from a meetup: > > > > > > > > > > > > > > > > > > http://mail-archives.apache.org/mod_mbox/oozie-user/201406.mbox/%3CCANjPD1TE2GdTqtFGYszBiPrOgLBB1Vd-r1cPHzuNFqjCtgq_Tw%40mail.gmail.com%3E > > > > > > > > The slides are: > > > > > http://www.slideshare.net/sportymona/oozie-meetup-slides-jun-3rd-2014 > > > > > > > > In the slides I noticed mention of one specific enhancement that got > me > > > > interested: > > > > > > > > Slide 5 ("Features - Usability") has a bullet that says "Updating > > > > coordinator definition on the fly". > > > > > > > > It's hard for me to tell without any more context if this slide is > > > talking > > > > about work that is progress, work that is already complete, or > perhaps > > > work > > > > that is planned? Can someone provide me any links or commentary to > > > explain > > > > in more detail what this means? I was trying to find something that > > > looked > > > > like this in the JIRA queue and I didn't see it but maybe I wasn't > > using > > > > the right keywords? > > > > > > > > Thanks, > > > > Ben > > > > > > > > > > -- > > > _____________________________________________________________ > > > The information contained in this communication is intended solely for > > the > > > use of the individual or entity to whom it is addressed and others > > > authorized to receive it. It may contain confidential or legally > > privileged > > > information. If you are not the intended recipient you are hereby > > notified > > > that any disclosure, copying, distribution or taking any action in > > reliance > > > on the contents of this information is strictly prohibited and may be > > > unlawful. If you have received this communication in error, please > notify > > > us immediately by responding to this email and then delete it from your > > > system. The firm is neither liable for the proper and complete > > transmission > > > of the information contained in this communication nor for any delay in > > its > > > receipt. > > > > > > > -- > _____________________________________________________________ > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify > us immediately by responding to this email and then delete it from your > system. The firm is neither liable for the proper and complete transmission > of the information contained in this communication nor for any delay in its > receipt. >
