Update HWReleaseProcess to allow RTL tagging independent of SW #196
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
calebofearth
requested review from
korran,
bharatpillilli,
JohnTraverAmd and
FerralCoder
|
calebofearth
commented
May 20, 2024
39 tasks
steph-morton
previously approved these changes
Jul 10, 2024
nquarton
reviewed
Jul 24, 2024
steph-morton
approved these changes
Jul 30, 2024
jlmahowa-amd
approved these changes
Aug 1, 2024
20 tasks
korran
approved these changes
Aug 1, 2024
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.
The current release process describes a sort of handshake between the RTL and SW repositories that means the repo caliptra-rtl may not be tagged for a major release until after the SW repo has consumed the RTL and published its own code. Software releases often lag RTL readiness (in particular, since ROM release precedes Runtime firmware).
The proposed process update allows RTL to be tagged when ready. Creation of a new RTL branch allows the Firmware team to consume a deterministic snapshot of the RTL, while the hardware team advances towards the next feature set on the main branch. This also resolves a current issue where the RTL consumed by Firmware as a submodule may diverge from the actual versioned RTL release.
See also: chipsalliance/caliptra-rtl#496