Skip to content

Commit 25df520

Browse files
palmer-dabbeltkito-cheng
authored andcommitted
Don't differ from the RVI definitions of terms like "frozen"
It's already confusing enough that these definitions are loosely applied, but having a comment in the spec source that's not even visible in the spec but re-defines these very important terms just adds an extra layer of complexity. Let's just use the RVI terms, that's what everyone else doesn't do. Signed-off-by: Palmer Dabbelt <[email protected]>
1 parent 9b6f43b commit 25df520

File tree

1 file changed

+0
-17
lines changed

1 file changed

+0
-17
lines changed

prelude.adoc

Lines changed: 0 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,4 @@
11
:company: RISC-V.org
2-
// These are the definitions from docs-template:
3-
//
4-
// development: Assume everything can change
5-
// stable: Assume everything could change
6-
// frozen: If you implement this version you assume the risk that something
7-
// might change because of the public review cycle but we expect
8-
// little to no change.
9-
// ratified: You can implement this and be assured nothing will change. If
10-
// something needs to change due to an errata or enhancement, it
11-
// will come out in a new extension. we do not revise extensions.
12-
//
13-
// These don't really make sense for our development process, so we replace
14-
// development with a single dev version that we brand as Pre-release, but
15-
// anything featuring in the document is implicitly frozen (in fact, stronger,
16-
// as frozen can still change in incompatible ways) as we cannot break ABI once
17-
// features are implemented in toolchains. Similarly stable is still frozen
18-
// just by another name for policy reasons.
192
:revlifecycle: frozen
203
:revnumber: 1.0-rc3-draft
214
ifeval::["{revlifecycle}" == "dev"]

0 commit comments

Comments
 (0)