+1 to releasing 2.8.0 - it's been a long time since 2.7.0 and a lot has been done.
I'd also like to release 2.7.1 in the near future, and will try to find time to be the RM for that. On 4 January 2017 at 14:15, Jim Apple <[email protected]> wrote: > Oh, and a specific topic for discussion: > > Should we include the docs in the source tarball? My feeling is yes, > but they are not really cleaned up yet, and so contain a lot of > Cloudera-specific info. > > Pros of including the docs in the tarball: Users get a docs tarball > from which they can build the hundreds of pages of usable > documentation. > > Cons: 1. Confused users about who runs the project. (Correct answer: > Apache Impala PPMC. Confused answer: Cloudera), 2. Possible failed > IPMC release vote that slows down the release. > I'd figure out a way to add a big caveat to the docs. Maybe on the landing page? Even better if there's a template we can add a caveat to that appears on every page. > > On Wed, Jan 4, 2017 at 2:09 PM, Jim Apple <[email protected]> wrote: > > This is not a [VOTE] thread. Everyone is encourage to participate. > > > > I am volunteering to be a release manager for 2.8.0. I am provisionally > testing > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=tree;h= > 4fa9270e647b9c097295dcc13d97136cca3139ad;hb=4fa9270e647b9c097295dcc13d9713 > 6cca3139ad > > > > to branch from. > > > > Are there any objections to releasing 2.8.0 soon? Keep in mind this is > > not your last chance to speak - there will be at least two votes one > > for PPMC releasing and one for IPMC releasing. See > > > > https://cwiki.apache.org/confluence/display/IMPALA/ > DRAFT%3A+How+to+Release >
