Document the Broker's versioning strategy #810
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
Member
djzager
commented
Mar 2, 2018
djzager
commented
- Document broker's compatibility with APBs
- Document versioning and branching strategy
openshift-ci-robot
added
the
size/M
jmrodri
approved these changes
Mar 3, 2018
docs/versioning.md
Outdated
| longer being added to the currently targeted OpenShift releases. When a new | ||
| branch is created, it will be named `release-MAJOR.MINOR` and the version in | ||
| the `master` branch will be bumped based on the rules in [Version | ||
| Format](#Version Format). |
There was a problem hiding this comment.
I think this should be Version Format
- Document broker's compatibility with APBs - Document versioning and branching strategy
shawn-hurley
requested changes
Mar 5, 2018
README.md
Outdated
|
|
||
| | ansible-service-broker | APB runtime 1 | APB runtime 2 | | ||
| |-----------------------------|---------------|---------------| | ||
| | ansible-service-broker 1.0 | ✓ | X | |
There was a problem hiding this comment.
Can we also put the v3.7, v3.9 tags here?
docs/versioning.md
Outdated
| targeted OpenShift Origin [release | ||
| v3.7.0](https://github.com/openshift/origin/releases/tag/v3.7.0). Following the | ||
| versioning rules, the version was bumped to `1.1.x` for OpenShift Origin [release | ||
| v3.9.0](https://github.com/openshift/origin/releases/tag/v3.9.0) and again to |
There was a problem hiding this comment.
This link does not appear to be working for me.
There was a problem hiding this comment.
Yeah. This is because v3.9.0 is not yet released. I could point it to the release-3.9 branch....not sure the best way to handle that.
There was a problem hiding this comment.
Oh duh, that was silly. I think that pointing to the branch, for now, makes sense. Should we just remember to come back and update that?
There was a problem hiding this comment.
We should. https://trello.com/c/iT8k66Zl/700-update-broker-readmemd-when-v390-is-released created for it.
shawn-hurley
approved these changes
Mar 5, 2018
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.