milleruntime commented on PR #2665: URL: https://github.com/apache/accumulo/pull/2665#issuecomment-1139585195
I think the design of this change is great so far but it is a major new feature, with a drastic increase in complexity, touching major parts of Accumulo (scans, API, metadata, configuration, scripts, and introduces another new server). I don't think this should get merged into 2.1. The complexity of this change on top of all the changes already in 2.1 will only further delay the release of 2.1. Main already has many major new features (ZK Prop Store, Overhaul of Compactions code, External Compactions, AMPLE, Master Rename, New Tracing, New Metrics, New SPI, Root Table change) not to mention the 1,130+ tickets marked done for 2.1. Here is a timeline of the past 4 years: - 2.0.0-alpha-1 was released 14 Oct 2018 and then 2.0.0-alpha-2 was released 31 Jan 2019 - Non-LTM 2.0.0 was released 02 Aug 2019 - LTM 1.10 was released 03 Sep 2020. - Bug fix release 1.10.1 was 22 Dec 2020 - Bug fix 2.0.1 was released 24 Dec 2020 - Sadly the first time ever, Accumulo did not have a release in 2021 :frowning_face: - Bug fix for 1.10.2 was 13 Feb 2022 I think 2.1.0 needs to be released ASAP so it can be tagged as an LTM. Users who are not on 1.10, should upgrade to 1.10.3. Users who upgraded to 2.0 at the time of release have been waiting 3 years (users who snagged the alpha will be 4 years) for the next LTM release. I think it would be a disservice to not have an LTM release this year. Our original plan was to Periodically release a new LTM approximately every 2 years. That being said Main may already be a major release and need to be called 3.0 so if that is the case, merge away! -- 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]
