Record the version decision: v1.1.0 stays on the v1 line, v2 is the next generation
Browse files
README.md
CHANGED
|
@@ -69,6 +69,17 @@ thresholds (open questions are listed at the end of that chapter), and one
|
|
| 69 |
naming example in `CONVENTIONS.md` that conflicts with `02_naming_conventions.md`
|
| 70 |
— chapter 02 is the authority where they disagree.
|
| 71 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 72 |
## Citation
|
| 73 |
|
| 74 |
See `CITATION.cff`. In short:
|
|
|
|
| 69 |
naming example in `CONVENTIONS.md` that conflicts with `02_naming_conventions.md`
|
| 70 |
— chapter 02 is the authority where they disagree.
|
| 71 |
|
| 72 |
+
## Versioning
|
| 73 |
+
|
| 74 |
+
**`v1.x` is this foundation being established.** The v1.1.0 expansion is large,
|
| 75 |
+
but size is not what moves the major number: everything in it belongs to the
|
| 76 |
+
same frontier foundation `v1.0.0` started — filled in, not replaced. The final
|
| 77 |
+
tag on this work will be `v1.1.0`.
|
| 78 |
+
|
| 79 |
+
**`v2.0.0` is reserved for the next generation of improvements** — thinking that
|
| 80 |
+
supersedes this foundation rather than completing it. Read a major bump here as
|
| 81 |
+
a genuine change of generation, not merely a big release.
|
| 82 |
+
|
| 83 |
## Citation
|
| 84 |
|
| 85 |
See `CITATION.cff`. In short:
|