Update Release Procedures With Git Tag Memo #3201
Merged
Conversation
This file contains hidden or 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
I have been running into issues with how VTR handles its versioning code. I have tracked the issue down to the tagged v9.0.0 release of VTR being off of another branch than Master. I added a small note to the release procedures to warn about this for the future.
|
@vaughnbetz Its really not that pressing of an issue that v9.0.0 is a tag of another branch than Master; but I have been running into issues with how downstream tools (like SiliconCompiler) track the version of VTR. Some users have been experiencing the version being set to "v9.0.0-candidate" which causes issues. Just added a small note to the release procedure about this since its not an obvious thing. |
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.
I have been running into issues with how VTR handles its versioning code. I have tracked the issue down to the tagged v9.0.0 release of VTR being off of another branch than Master.
I added a small note to the release procedures to warn about this for the future.