Skip to content

Instantly share code, notes, and snippets.

@ikedas
Last active October 11, 2018 03:21
Show Gist options
  • Save ikedas/d572c65812f58435775872c0126bb46e to your computer and use it in GitHub Desktop.
Save ikedas/d572c65812f58435775872c0126bb46e to your computer and use it in GitHub Desktop.
Sympa 7 versioning scheme [DRAFT]

Sympa 7 versioning scheme [DRAFT]

Here versioning scheme for Sympa 7 is described.

Format of version string is one of following:

<major>.<minor>-<pre>
<major>.<minor>.<micro>

A version string consists of following parts:

  • <major> is major version number. It is always 7.

  • <minor> is minor version number. It should be increased whenever significant changes or additions are made.

  • One of <pre> and <micro> should exist.

    • <pre> is pre-release version. alpha, beta or either of them suffixed by number, e.g. alpha11, beta3.

    • <micro> is post-release patch level. It should begin with 0 by each minor version, and should be increased when insignificant changes or fixes are made.

Examples

  • 7.0.0

  • 7.1-beta

  • 7.1-beta2

  • 7.1.22

Bad examples

These are bad examples and should not really be used.

  • 7.0

    No <pre> nor <micro>.

  • 7.1.2-beta

  • 7.1-beta.2

  • 7.1-beta2.0

    Both <pre> and <micro> appear.

  • 7.1.22.1

    Has the level lower than patch level (patch level with multiple columns does not matter).

Application

  • This scheme will be applied to pre-release and stable versions of Sympa 7. Note that this scheme is not applied to prior versions of Sympa, 6.2.x and earlier.

  • However, until the community will have reached a consensus that the first stable version of Sympa 7 should be released, 7.0-alpha<n> (<n> is a number) will solely be used as version string.

@racke
Copy link

racke commented Feb 24, 2018

What about good examples :-).

@ikedas
Copy link
Author

ikedas commented Feb 25, 2018

Added. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment