The L & N fixes just went out, I’m working to push out 2.7.3 - running into a Nexus issue. Once that goes out, I’ll immediately do a 2.8.0.
Like I requested before in one of the 3.x threads, can we just line up 3.0.0-alpha1 right behind 2.8.0? That simplifies most of this confusion, we can avoid splitting the bandwidth from the community on fixing blockers / vetting these concurrent releases. Waiting a little more for 3.0.0 alpha to avoid most of this is worth it, IMO. Thanks +Vinod > On Jul 21, 2016, at 11:34 AM, Andrew Wang <andrew.w...@cloudera.com> wrote: > > Hi all, > > Since we're planning to spin releases off of both branch-2 and trunk, the > changelog for 3.0.0-alpha1 based on JIRA information isn't accurate. This > is because historically, we've only set 2.x fix versions, and 2.8.0 and > 2.9.0 and etc have not been released. So there's a whole bunch of changes > which will show up for the first time in 3.0.0-alpha1. > > I think I can write a script to (carefully) add 3.0.0-alpha1 to these > JIRAs, but I figured I'd give a heads up here in case anyone felt > differently. I can also update the HowToCommit page to match. > > Thanks, > Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
