Tied v1.x with Extensibility v0.1.x #50
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
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
Tied Gerrit plugin v1.x with GE Extensibility v0.1.x.
Planning to tie v2.x with GE Extensibility v0.2.x. Or is It better to be consistent with GE version and do Gerrit plugin v3.5? Any thoughts?
What is the current behavior?
Gerrit plugin v1.x could be used in any GE version. I think it is better to restrict Gerrit plugin v1 for GE .net framework usage, and Gerrit plugin v2 (or 3.5?) with GE .net5.
What is the new behavior?
Gerrit plugin v1.3.2 should not be used in GE version >=3.5. I'm going to release a new Gerrit plugin version for GE >=3.5.
Does this PR introduce a breaking change?