Use normal versioning system (semver?) #3

New Issue

rudzik8 · 2022-05-16T16:48:53+02:00

rudzik8 commented

2022-05-16 16:48:53 +02:00

Currently, every release is marked like this: YYYY-MM-DD. If two releases releases made in one day, second is named like YYYY-MM-DDfix, third like YYYY-MM-DDfix2 and so on.
This system is really weird and strange. We need to change that

Options:

Start using semver (which is MAJOR.MINOR.PATCH), counting from v1.0.0
Start using versys I've used for mcl_decor (which is MAJOR.MINOR_PATCH), counting from v1.0_00
Start using most primitive rolling versys (like rolling-RELEASENUMBER)

Each option (even last one) will be better than our current crappy date(+fix) versioning

Currently, every release is marked like this: `YYYY-MM-DD`. If two releases releases made in one day, second is named like `YYYY-MM-DDfix`, third like `YYYY-MM-DDfix2` and so on. This system is really weird and strange. We need to change that ### Options: * Start using [semver](https://semver.org/) (which is `MAJOR.MINOR.PATCH`), counting from **v1.0.0** * Start using versys I've used for [mcl_decor](https://git.minetest.land/rudzik8/mcl_decor/releases) (which is `MAJOR.MINOR_PATCH`), counting from **v1.0_00** * Start using most primitive rolling versys (like `rolling-RELEASENUMBER`) Each option (even last one) will be better than our current crappy date(+fix) versioning

rudzik8 added the

discussion

label 2022-05-16 16:48:53 +02:00

rudzik8 changed title from ~~Use normal versioning system (symver?)~~ to Use normal versioning system (semver?)

2022-05-18 08:40:27 +02:00

rudzik8 closed this issue

2024-02-22 13:43:10 +01:00

This repo is archived. You cannot comment on issues.