Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

errata process #5

Open
wmat opened this issue Oct 1, 2024 · 4 comments
Open

errata process #5

wmat opened this issue Oct 1, 2024 · 4 comments

Comments

@wmat
Copy link
Contributor

wmat commented Oct 1, 2024

I have yet to see the errata process documented in the RISC-V Specifications Repos chapter followed. Do we need to re-address this process and/or begin enforcing it?

@kersten1
Copy link
Contributor

kersten1 commented Oct 1, 2024

Where is that policy document?

@kersten1
Copy link
Contributor

kersten1 commented Oct 1, 2024

@jjscheel

@wmat
Copy link
Contributor Author

wmat commented Oct 1, 2024

It's 13.2.3 RISC-V Specificaions Repos

@jjscheel
Copy link
Collaborator

jjscheel commented Oct 1, 2024

Ah,, now I understand what you're saying. You're saying that no one follows this statement:

  • Each ISA specification repo must contain an errata folder.
    • The folder must contain text files which detail the errata and include the date the errata was first
      documented.
  • If any errata are resolved in a future commit, do not remove the errata. Mark it as fixed and give the
    SHA of the commit where the errata was addressed.

Is that it?

I do agree we haven't done that.

So, part of what we'll need to do is clean up the policies with areas which need to either be updated, removed, etc. So, this is a a good issue to keep. Please make sure we put all text and full reference in here when we re-visit in the coming months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants