Skip to main content

Under Development

RISC-V members collaborate, develop, maintain, and ratify RISC-V specifications.

VIEW DEVELOPMENT SPECSBROWSE WIKI

The development process for all RISC-V specifications is open, transparent, and primarily conducted on GitHub.

However, to contribute to the development of specifications, you must be a member of RISC-V International.

LEARN HOW TO CONTRIBUTE

The Specification Lifecycle

The RISC-V specification process involves a sequence where an idea is proposed, planned, developed, frozen for review, publicly reviewed and refined, and finally ratified as an official standard.

1

Inception

This is the starting point. Someone — either an individual or a committee — within the RISC-V community suggests a new idea for a specification or an extension. Think of it as the "spark" that gets things going!
2

Plan

Now we focus on creating a plan. RISC-V Members map out the timeline, figure out what resources are needed, and set the rules to guide the process. This includes deciding when and how the public will get a chance to review the work.
3

Develop

This is the heart of the process. RISC-V Members actively create and refine the specification. Everyone works together to ensure it meets the agreed milestones and quality checks.
4

Freeze

At this stage, everything is locked in place. No big changes are allowed, and the specification is now prepared for public review. This means it's almost ready for the final stages!
5

Public Review & Ratification-Ready

The draft is shared publicly, allowing everyone — whether RISC-V Members or not —to provide feedback and suggestions. All comments must be addressed, ensuring everything is in top shape for the final approval process. When it's "Ratification-Ready," it's good to go for formal approval!
6

Final Stage: Ratified

Once ratified, the specification becomes an official standard, sealed and ready for the world to use!