Skip to content
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

Open
ypid opened this issue Jul 9, 2016 · 3 comments
Open

Migration/upgrade notes #160

ypid opened this issue Jul 9, 2016 · 3 comments

Comments

@ypid
Copy link
Member

ypid commented Jul 9, 2016

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

@drybjed
Copy link
Member

drybjed commented Jul 9, 2016

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.

@ypid ypid added the approved label Jul 9, 2016
@ypid
Copy link
Member Author

ypid commented Jul 9, 2016

Agreed 😉 Done.

ypid added a commit to ypid/ansible-owncloud that referenced this issue Jul 14, 2016
@ypid
Copy link
Member Author

ypid commented Jul 14, 2016

@drybjed Proposed to put the migration scrips into docs/scripts. This enhancement goes in line with #145. So this idea could have come from me 😄

https://github.com/ypid/ansible-owncloud/blob/rework-3/docs/scripts/upgrade-from-v0.2.X-to-v0.3.X

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants