We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
docs(VERSION): adopt the `M.np.Q.R` interpretation; "current versioning scheme" -> "2018 versioning scheme"
docs(VERSION): update descriptions for RELEASE & CURRENT; update EOL info; add branch links; group releases by branches; fix minor typos
docs(VERSION): add `CODENAME` for v3.0 & v3.1; add plans for v3.1
docs(VERSION): add `N`/`CODENAME` omitting convention
docs(VERSION): cancel the projected official status of `DreamBBS-202X` names
docs(VERSION): add `CODENAME` to versioning scheme; denote the aka. name(s) with `/`; document fields `CODENAME` & `PRERELEASE`
docs(VERSION): hyphenate adjective words; fix typos: branchs -> branches
docs(VERSION): add `v4.N`/`4D.N` roadmap
docs(VERSION): fix missing article "the"s in the version scheme description for CURRENT
docs(VERSION): clarify terminologies: "branch series" for RELEASE & CURRENT; "version series" for `v0.N`/`vM.0`; "special editions" for non-canon versions
docs(VERSION): `<user or team>` -> `<user-or-team>`: improve readability
docs(VERSION): refine development workflow: `master` -> `stable` tag; `develop` -> `master`; PRs now belong to `<user>/develop`
docs(VERSION): `M.N.` -> `M.N.P`: fix typo
docs(VERSION): update status
docs(VERSION): name the 2018 versioning scheme to avoid confusions
docs(VERSION): add `MD.N.P.Q` legacy versioning notation
docs(VERSION): reword: viable -> acceptable; convention -> conventions
docs(VERSION): reassign version field letter: `X.Y.Z` -> `M.N.P`; reword
docs: 3.20 -> 3.21 for legacy version of v3
chore(Release Branch): change v2.1.0 to v2.1-rc1; add release link; mark it as pre-release–only
chore(Release Branch): only use checkboxes for ongoing branches; mark v3.0 as in the test stage
docs(Branches of Development): add info of the new development workflow after v3.0
Add link to the branch of the special release versions; add more feature description to v4.20-alpha
"Special Release Version" -> "Special Release Versions"
Add paragraph "Special Release Version"
Update information for v3.0
`DreamBBS-2020` -> `DreamBBS-202X`: Rename due to minor changes of the release plan
Remove the trailing character `g` due to editing errors
Add links to the release notes to version numbers
Cancel the plan for `develop` branch in v3.0 in favor of keeping only the `master` branch