https://github.com/apache/accumulo/pull/295 is likely a blocker bug, but I don't really know the full implications of the breakage to the replication system. It is currently marked under Mike Miller's ACCUMULO-4662, rather than a separate issue.
On Thu, Aug 31, 2017 at 9:57 AM Michael Wall <mjw...@gmail.com> wrote: > You are correct Mike, my mistake. I was looking at > https://issues.apache.org/jira/projects/ACCUMULO/versions/12339245. Click > the "issues in progress". Thanks for keeping me honest. > > On Thu, Aug 31, 2017 at 9:46 AM Mike Miller <michaelpmil...@gmail.com> > wrote: > > > The only one I have open for 1.8.2 is > > https://issues.apache.org/jira/browse/ACCUMULO-4662. I will look around > > for > > any more spots in the code that need to be fixed but I think its pretty > > much done. > > > > Was this the other ticket you were talking about Mike? > > https://issues.apache.org/jira/browse/ACCUMULO-4342. Its currently > > assigned > > to you. > > > > On Thu, Aug 31, 2017 at 9:17 AM, Michael Wall <mjw...@gmail.com> wrote: > > > > > Mike Miller has 2 tickets in progress and the issue Keith mention is > the > > > only blocker I saw. Once those are complete, I am in favor of a 1.8.2 > > > release. I am happy to do the release again and continue as the 1.8 > > > release manager. I am also happy to help someone else do that. It is > a > > > patch release, but we typically still run the continuous ingest > testing. > > > Christopher, do we still have resources to do that? > > > > > > On Wed, Aug 30, 2017 at 5:34 PM Keith Turner <ke...@deenlo.com> wrote: > > > > > > > I Am in favor of that after I finish fixing ACCUMULO-4669 > > > > > > > > On Wed, Aug 30, 2017 at 2:16 PM, ivan bella <i...@ivan.bella.name> > > > wrote: > > > > > Is it time to consider talking about tagging a 1.8.2 release? > > > > > > > > > >