+1 for releasing a 1.7.2 (and even a 1.6.6) in short order. On Thu, May 26, 2016 at 1:14 PM Keith Turner <[email protected]> wrote:
> On Thu, May 26, 2016 at 1:04 PM, Sean Busbey <[email protected]> wrote: > > > Do the folks assigned to those issues believe they'll be ready by e.g. > > Wednesday next week? > > > > I think I can get ACCUMULO-4314 done quickly because its just taking a > subset of work done for ACCUMULO-1124. If I can not get to it, I don't > want to hold things up. I'm in favor of a deadline of next week Wed. > > > > > > Since it's been ~3 months I'd rather release the stuff we have if > > it'll take much longer than that. I'd be willing to commit to RM a > > 1.7.3 in a month if it makes folks more comfortable bumping things > > out. > > > > On Thu, May 26, 2016 at 9:48 AM, Mike Drob <[email protected]> wrote: > > > I made a first pass at triaging issues; apologies for the JIRA spam. > > > > > > I've deferred most issues that were either trivial or minor or > > unassigned, > > > so we are currently left with 10 open, most of which look like IT > > failures > > > and also apply to 1.8.0. I'm currently thinking that ACCUMULO-4157, > > > ACCUMULO-4314, and ACCUMULO-2990 may be the only issues worth waiting > on. > > > > > > Mike > > > > > > On Wed, May 25, 2016 at 11:43 PM, Keith Turner <[email protected]> > wrote: > > > > > >> i would like to get ACCUMULO-4314 in for 1.7.2. > > >> > > >> https://issues.apache.org/jira/browse/ACCUMULO-4314 > > >> > > >> On Wed, May 25, 2016 at 6:34 PM, Mike Drob <[email protected]> wrote: > > >> > > >> > Following up on the 1.8.0 release thread, maybe we should also get a > > >> 1.7.2 > > >> > release going as well. I'll probably go through and move issues out > to > > >> > 1.7.3 either this week or next week. Does anybody have issues that > > they > > >> > believe are blockers for 1.7.2? > > >> > > > >> > Mike > > >> > > > >> > > > > > > > > -- > > busbey > > >
