I think [3] is OBE and can be closed. On Mon, Apr 4, 2022 at 9:11 AM Mike Miller <mmil...@apache.org> wrote:
> Yes I agree, that was the goal of this email thread. I found a few more > tickets that should be addressed for the next release. > > Ivan - There was some work done on this PR but it has been some time. Do > you want to take a look at it? Implement a Thread limit. [1] > Keith T - I think we should get this one merged to fix that consistency > check bug I found. It looks like it is finished. [2] > Dave & Dom - Were you guys able to figure out a fix for the new external > compaction metrics test? [3] > > FYI we have 6 blockers for 2.1: > https://github.com/apache/accumulo/labels/blocker > > This is almost definitely going into 2.1 [4]. Thanks Jeff! > > [1] https://github.com/apache/accumulo/pull/1487 > [2] https://github.com/apache/accumulo/pull/2574 > [3] https://github.com/apache/accumulo/issues/2406 > [4] https://github.com/apache/accumulo/pull/2215 > > On Fri, Apr 1, 2022 at 2:21 PM Dave Marion <dmario...@gmail.com> wrote: > > > I think it would be useful to do some release planning so that we know > what > > features we are working towards and in which release they will be in. > This > > would be helpful for determining what existing PRs need to make it into > > 2.1.0. 2.1.0 is the LTM release, so patches for existing features will be > > backported (2.1.1, 2.1.2, 2.1.3, etc.) However, as defined in [1], > features > > that don't make it into 2.1.0 will go into the next non-LTM release > (2.2.0) > > and any patches to bugs in those features will go into the next non-LTM > > release after that (2.3.0). > > > > I'm not trying to hold up the 2.1.0 release by suggesting that we perform > > this activity. I'm just asking what the future holds, even if it's just > one > > feature in the next non-LTM release. My concern is that the next release > > will be open-ended and anything not included in 2.1.0 might not get put > > into a release for a very long time. > > > > [1] https://accumulo.apache.org/contributor/versioning.html#LTM > > > > > > On Thu, Mar 31, 2022 at 11:43 AM Mike Miller <mmil...@apache.org> wrote: > > > > > Starting an email chain of things that folks want to finish for 2.1. > Here > > > is what we currently have in the works that are most likely going into > > 2.1: > > > https://github.com/apache/accumulo/pull/2569 > > > https://github.com/apache/accumulo/pull/2600 > > > https://github.com/apache/accumulo/pull/2293 > > > > > > Some things that may go into 2.1: > > > https://github.com/apache/accumulo/pull/2422 > > > https://github.com/apache/accumulo/pull/2475 > > > https://github.com/apache/accumulo/pull/2197 > > > > > > I created a Project for follow on work to the ZK property change. I was > > > planning on putting tasks in there that we want to complete for 2.1. > But > > we > > > could also use it for post 2.1 work. > > > https://github.com/apache/accumulo/projects/24 > > > https://github.com/apache/accumulo/issues/2469 > > > > > > FYI a draft copy of the release notes has already been on the website: > > > https://accumulo.apache.org/release/accumulo-2.1.0/ > > > > > > This may be a good thread to discuss whether or not a task needs to go > > into > > > 2.1 or should wait for the next version. We currently have 32 open pull > > > requests so please email me if there is one that you would like > > prioritized > > > for 2.1. > > > > > >
