accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Wall (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-4479) UPGRADING.md
Date Thu, 09 Feb 2017 15:51:41 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Wall resolved ACCUMULO-4479.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.3

> UPGRADING.md
> ------------
>
>                 Key: ACCUMULO-4479
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4479
>             Project: Accumulo
>          Issue Type: Task
>          Components: docs
>    Affects Versions: 1.8.0
>            Reporter: Christopher Tubbs
>            Assignee: Michael Wall
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>
>         Attachments: UPGRADING.md
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> UPGRADING.md was not updated for the 1.8.0 release. I actually didn't even realize we
were putting notes about specific upgrade paths in a per-release way inside our release.
> This is prone to being overlooked and forgotten. We should have generic version-agnostic
information in UPGRADING.md, and put more specific per-release notes in an UPGRADING section
on the release notes for specific upgrade issues. At the very least, the version of this document
for the current release does not need to contain upgrade instructions for upgrading to previous
releases.
> The more information we have in our documentation which is written to correspond to the
current/next release, the more (undocumented) manual steps are involved for a release manager,
and the more likely these steps are going to get overlooked and forgotten.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message