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 <[email protected]> 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.
>

Reply via email to