dlmarion commented on issue #3092:
URL: https://github.com/apache/accumulo/issues/3092#issuecomment-1331229769
> But it's the "more branches to maintain" that I'm hoping to avoid.
I agree, that's a concern.
> However, I'd rather focus on 3.0, and put the proposed additions there. I
just don't see much urgency to include these proposed features as a 2.x update
instead of just rolling them into 3.0.
I think the issue here is that:
1. 2.1 was decided as a LTM release too early
2. we don't have a timeline for 3.x
I would be on board with moving my features to 3.x if I knew more about its
timeline. In fact, I would propose something like (dates are hypothetical):
3.0.0 - removal of deprecated items only (release date January or February
- as early as possible)
3.1.0 - feature set A (release June 2023)
3.2.0 - feature set B (release Dec 2023)
LTM - when we're done and need to make breaking changes for 4.x
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
