Github user ctubbsii commented on the issue:
https://github.com/apache/accumulo/pull/212
Repeating what I said in the JIRA, I don't think it's useful to provide
static upgrade instructions for specific upgrade paths, where it's prone to
being out-of-date (and possibly outright incorrect). The documentation should
point to the most up-to-date docs on the website, specifically the an upgrading
section of the release notes, which we can create upon release, and keep
updated as we find issues affecting upgrade interoperability.
I also don't think it's useful to document upgrade paths to older releases
in the current one. It's a bit like if Microsoft Windows 2010 installation
documentation contained upgrade instructions from Windows 95 to Windows 98. It
doesn't make sense to me.
If it were entirely up to me, I'd simply delete this file and make it a
point to have an UPGRADING section on every release notes from here on.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
