-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration/upgrade notes #160
Comments
Sure, separate file in the root directory (easily visible) describing any needed upgrade steps sounds good. I don't think that it needs to always be present, only when we know that some manual upgrade steps are needed or expected. |
Agreed 😉 Done. |
Updates proposal: debops/docs#160
@drybjed Proposed to put the migration scrips into https://github.com/ypid/ansible-owncloud/blob/rework-3/docs/scripts/upgrade-from-v0.2.X-to-v0.3.X |
Updates proposal: debops/docs#160
Related to the redesign of the changelog format in #154 it might also be a good idea to think about migration/upgrade notes.
http://keepachangelog.com/ also has a discussion about that: olivierlacan/keep-a-changelog#34
Previously used:
I would propose keeping a separate
UPGRADE.rst
file when needed in the root of the repo and integrate it into the docs after the changelog.Reasons for a separate changelog: olivierlacan/keep-a-changelog#34 (comment)
Example: https://github.com/ypid/ansible-owncloud/blob/rework-3/UPGRADE.rst
The text was updated successfully, but these errors were encountered: