Version 0.1.0 #235
Merged
Version 0.1.0 #235
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
Those should not appear in the release. The initial release is a bit of a special case where just removing them is fine as there's no previous release to upgrade from. For later releases, they would have to be combined into a 0.2.0.sql instead.
julianbrost
force-pushed
the
release-v0.1.0
branch
from
bff56c1 to
6facf38
Compare
|
Apart from this PR, the only other thing that should make it into the |
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.
Changes in here are inspired by the Icinga DB release checklist (
AUTHROSupdate was already done in #234).The schema upgrade files were removed as they were mostly useful during development, with this release, 0.1.0 serves as the new baseline. The initial release is a bit of a special case where just removing them is fine as there's no previous release to
upgrade from. For later releases, they would have to be combined into a 0.2.0.sql instead.