docs: Major version in case of server change(s) #1918
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -58,6 +58,7 @@ We aim to support [Baseline](https://developer.mozilla.org/en-US/blog/baseline-e | |||
|
|
|||
| * when we bump Django to a major version | |||
| * when we change how we store data (both in database and filesystem) | |||
| * when we make required changes on the server (for people maintaining instances) | |||
There was a problem hiding this comment.
Sounds a bit broad to me, not every change on the server should require a major (eg. updating the settings is a server change). Something like when we change how uMap can be deployed ?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.