This is starting to diverge from the original topic :) But I would like to say (1) If we are treating branch-2/2.0 as the final, last 2.x release, we should be proactive in updating dependencies. I did a quick search and found a lot of dependencies in branch-2 are very old, and some are even susceptible to known vulnerabilities. We did a lot in 3.x, some are even backward-incompatible. But I guess we didn't imagine people are still on 2.x a few years after 3.x went GA.
(2) I wrote a summary for the last Hadoop Contributor Meetup, and circulated it internally. It wasn't meant for public consumption, but if it helps, I can publish it here in the mailing list. We will also have an upcoming blog post on the meetup at Cloudera's website, too. On Mon, Aug 26, 2019 at 9:16 AM Sean Busbey <bus...@cloudera.com.invalid> wrote: > On Mon, Aug 26, 2019 at 9:20 AM Eric Badger <ebad...@verizonmedia.com> > wrote: > > > > - Stuff has been going into branch-2 sporadically but I don't who is > > actively > > using that code other than as part of a cherrypick backwards strategy. > > > > - Should we do a 2.10.x release? Or just say "time to upgrade?" > > > > We have talked at a few different Hadoop contributors meetups and > community > > syncs and agreed that 2.10 should serve as a "bridge" release for 3.x so > > that 2.x clients can talk to 3.x servers and vice versa without > > compatibility issues. At the last meeting where we discussed this it > seemed > > that there were 3 major compatibility issues. The biggest one was in the > > edit logs. > > > > > Just a quick friendly reminder to everyone that stuff has to make it > to the mailing lists for Hadoop for it to be considered a discussion > that happened "in the community". Especially decisions and the > discussions that lead to them have to happen on our mailing lists and > not at in person events. > > -- > busbey > > --------------------------------------------------------------------- > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org > >
