Hi Alejandro, Thanks for completing the release of Oozie 3.3.0 and doing the cleanups. I will be glad to volunteer for 3.3.1 release.
Thanks, Virag On 12/3/12 4:45 PM, "Alejandro Abdelnur" <[email protected]> wrote: >I've just completed the release of Oozie 3.3.0 (pushing bits, updating >site, tags, JIRAs) > >While I was at it I've noticed that a few commits went into the branch-3.3 >after tagging the release (OOZIE-1064, OOZIE-1065, OOZIE-1100, >OOZIE-1099). >Those JIRAs were incorrectly logged under Oozie 3.3.0, I've updated the >release release log moving them to Oozie 3.3.1. I've done this in trunk >and >in branch-3.3. I've also updated the JIRAs accordingly. > >I've marked the JIRA version 3.3.0 as released and created a new JIRA >version 3.3.1. All open JIRAs marked as fix in 3.3.0 have been moved to >3.3.1. I'd suggest that in the future, we only set the FIXEDVERSION when >resolving the JIRA. > >Going back to the commits to branch-3.3 post 3.3.0 release. Is any >committer volunteering to drive 3.3.1 release? Also, we should see of all >the commits in trunk, which ones we want backported for a 3.3.1 release. > >Thx > >-- >Alejandro
