Bump to 2.6.0-snapshot #22
Merged
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
|
@aledsage Shouldn't do a release of |
aledsage
force-pushed
the
bump-to-depend-on-0.13-snapshot
branch
from
9868e23
to
ed2e2e6
Compare
aledsage
changed the title
|
@tbouron we don't need to release 2.5.0 before bumping to 2.6.0-snapshot, but agree we should release a 2.5.0. In the same way, in brooklyn we bump master's version while working on the release candidates of a given brooklyn release. I think it's most important to bump the version before we change a major Brooklyn dependency, if we intend to release a 2.5.0 against the previous stable brooklyn version. I'll create a 2.5.x branch that we can release from. |
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.
Please first merge #21 (so that 2.5.0-snapshot can depend on brooklyn 0.12.0).