ctubbsii commented on a change in pull request #45: ACCUMULO-4747 Create a unified upgrade reference URL: https://github.com/apache/accumulo-website/pull/45#discussion_r154780260
########## File path: _docs-2-0/administration/upgrading.md ########## @@ -0,0 +1,110 @@ +--- +title: Upgrading Accumulo +category: administration Review comment: @jmark99 Understood. I'm thinking ahead, to the situation where the 2.0 upgrade section of the docs doesn't fully describe a situation for 2.0.9, because of some bug which specifically affected the 2.0.8 to 2.0.9 upgrade (as an example). Would this get added to the main 2.0 docs, or just called out in the 2.0.9 release notes? Or both? Are we prepared to put all patch-specific upgrade notes in the major-minor release notes, or would we want to describe the overall process, and mention "check the release notes for your version, for any upgrade issues specifically for that version"? I don't feel strongly about one way or another. I just want to have a plan in place for when we encounter this scenario. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
