Skip to content

Versions and names

Daniel Báez edited this page Dec 11, 2024 · 1 revision

We have a problem. For agility we work in two branchs, v3001 and master where we do bug fixes and new features. We don't separate them. This gives us another problem, we can't release the bug fixes without release the new versions. We could release them as betas but doesn't make much sense, because bugs should come to stables as soon as possible.

Solution 1

Release the bug fixes with the new features but as "experimental". They can change, so we let know users that, but we also give new bug fixes. For that, there's two proposals for the versioning.

Ver 1.

  • 3000.0.X: It means bug fixes, without any new experimental feature
  • 3000.X.0: It means added experimental features
  • 30XX.0.0: It means experimental features becoming stable, for example, 3001, 3002, 3003
  • XX00.0.0: It means new stable with breaking changes, for example, 4000, 5000, 6000

It have some troubles, first the "stable" (3rd) has a limit of two digit, we could release 3099 and then we can't release more without going to the next stable, 4000. Otherwise, we already did it with 3000 and 3001, 3001 don't introduce breaking changes, only features.

Ver 2.

  • 3000.0.X: It means bug fixes and added experimental features
  • 3000.X.0: It means experimental features becoming stable
  • XXXX.0.0: It means breaking changes
Clone this wiki locally