ctubbsii commented on issue #3092: URL: https://github.com/apache/accumulo/issues/3092#issuecomment-1324533452
Regardless of where you track this list (and I would prefer a "project" (we've been using the "classic" projects) over an issue that is more easily lost, I don't think we need to include things that are already staged for a 2.1 patch release, unless we're trying to argue that the 2.2 should replace the 2.1 as a continuation of that "LTM" series. But, that could get really confusing, suggesting that risk-averse users jump a minor release when they chose to stay on LTM releases to avoid the risks associated with new features. Then again, we can just say "oops, our mistake", 2.1.0 is not an LTM release, but 2.2.0 is. But then, when does it stop? Maybe next time we do a .0 release, we do an initial release as non-LTM, and then only decide it's going to be an LTM release later? I don't know what's least confusing to users trying to track the version hell. -- 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]
