Skip to content

Revisions

  • docs(VERSION): adopt the `M.np.Q.R` interpretation; "current versioning scheme" -> "2018 versioning scheme"

    @IepIweidieng IepIweidieng committed Dec 3, 2023
  • docs(VERSION): update descriptions for RELEASE & CURRENT; update EOL info; add branch links; group releases by branches; fix minor typos

    @IepIweidieng IepIweidieng committed Dec 3, 2023
  • docs(VERSION): add `CODENAME` for v3.0 & v3.1; add plans for v3.1

    @IepIweidieng IepIweidieng committed Nov 7, 2022
  • docs(VERSION): add `N`/`CODENAME` omitting convention

    @IepIweidieng IepIweidieng committed Nov 7, 2022
  • docs(VERSION): cancel the projected official status of `DreamBBS-202X` names

    @IepIweidieng IepIweidieng committed Nov 7, 2022
  • docs(VERSION): add `CODENAME` to versioning scheme; denote the aka. name(s) with `/`; document fields `CODENAME` & `PRERELEASE`

    @IepIweidieng IepIweidieng committed Nov 7, 2022
  • docs(VERSION): hyphenate adjective words; fix typos: branchs -> branches

    @IepIweidieng IepIweidieng committed Nov 7, 2022
  • docs(VERSION): add `v4.N`/`4D.N` roadmap

    @IepIweidieng IepIweidieng committed Nov 3, 2022
  • docs(VERSION): fix missing article "the"s in the version scheme description for CURRENT

    @IepIweidieng IepIweidieng committed Nov 3, 2022
  • docs(VERSION): clarify terminologies: "branch series" for RELEASE & CURRENT; "version series" for `v0.N`/`vM.0`; "special editions" for non-canon versions

    @IepIweidieng IepIweidieng committed Nov 3, 2022
  • docs(VERSION): `<user or team>` -> `<user-or-team>`: improve readability

    @IepIweidieng IepIweidieng committed Sep 19, 2022
  • docs(VERSION): refine development workflow: `master` -> `stable` tag; `develop` -> `master`; PRs now belong to `<user>/develop`

    @IepIweidieng IepIweidieng committed Sep 19, 2022
  • docs(VERSION): `M.N.` -> `M.N.P`: fix typo

    @IepIweidieng IepIweidieng committed Sep 19, 2022
  • docs(VERSION): update status

    @IepIweidieng IepIweidieng committed Sep 19, 2022
  • docs(VERSION): name the 2018 versioning scheme to avoid confusions

    @IepIweidieng IepIweidieng committed Sep 19, 2022
  • docs(VERSION): add `MD.N.P.Q` legacy versioning notation

    @IepIweidieng IepIweidieng committed Sep 19, 2022
  • docs(VERSION): reword: viable -> acceptable; convention -> conventions

    @IepIweidieng IepIweidieng committed Sep 19, 2022
  • docs(VERSION): reassign version field letter: `X.Y.Z` -> `M.N.P`; reword

    @IepIweidieng IepIweidieng committed Sep 19, 2022
  • docs: 3.20 -> 3.21 for legacy version of v3

    @IepIweidieng IepIweidieng committed Apr 24, 2021
  • chore(Release Branch): change v2.1.0 to v2.1-rc1; add release link; mark it as pre-release–only

    @IepIweidieng IepIweidieng committed Apr 4, 2021
  • chore(Release Branch): only use checkboxes for ongoing branches; mark v3.0 as in the test stage

    @IepIweidieng IepIweidieng committed Apr 4, 2021
  • docs(Branches of Development): add info of the new development workflow after v3.0

    @IepIweidieng IepIweidieng committed Apr 4, 2021
  • Add link to the branch of the special release versions; add more feature description to v4.20-alpha

    @IepIweidieng IepIweidieng committed Apr 2, 2021
  • "Special Release Version" -> "Special Release Versions"

    @IepIweidieng IepIweidieng committed Apr 2, 2021
  • Add paragraph "Special Release Version"

    @IepIweidieng IepIweidieng committed Apr 2, 2021
  • Update information for v3.0

    @IepIweidieng IepIweidieng committed Apr 2, 2021
  • `DreamBBS-2020` -> `DreamBBS-202X`: Rename due to minor changes of the release plan

    @IepIweidieng IepIweidieng committed Jan 6, 2021
  • Remove the trailing character `g` due to editing errors

    @IepIweidieng IepIweidieng committed Jan 6, 2021
  • Add links to the release notes to version numbers

    @IepIweidieng IepIweidieng committed Jan 1, 2021
  • Cancel the plan for `develop` branch in v3.0 in favor of keeping only the `master` branch

    @IepIweidieng IepIweidieng committed Jan 1, 2021