Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: "Michael Ströder" <>
Subject: [Galene] Re: 0.4 tag & locked/unlocked state available?
Date: Fri, 16 Jul 2021 16:30:02 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 7/16/21 4:15 PM, Juliusz Chroboczek wrote:
>> Please do not tag as because with semantic versioning this
>> would be a release newer than 0.3.0 and not a 0.4.0 pre-release.
> Do you have any better suggestions?

See the suggested ordering matching rules in semantic versioning:

The question is whether a tag is really needed by client devs.

When packaging Galène from latest git revision I usually use a package
base version like this:


With 0.4.0 being the next planned revision.

Package version would then be something like:


Some downstream packagers sometimes use git revisions instead of a
timestamp. Personally I prefer monotonically increasing timestamps.

AFAIK the tilde is commonly used by downstream packagers for suffixing
pre-releases because 0.4.0-1 would considered be a later release
following 0.4.0~<whatever> by package managers.

Ciao, Michael.

  parent reply	other threads:[~2021-07-16 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 13:11 [Galene] " Jeroen van Veen
2021-07-16 14:06 ` [Galene] " Juliusz Chroboczek
2021-07-16 14:13   ` Michael Ströder
2021-07-16 14:15     ` Juliusz Chroboczek
2021-07-16 14:18       ` Gabriel Kerneis
2021-07-16 14:30       ` Michael Ströder [this message]
2021-07-19 11:10         ` [Galene] Re: tagging and semver Juliusz Chroboczek
2021-07-16 14:16   ` [Galene] Re: 0.4 tag & locked/unlocked state available? Jeroen van Veen
2021-07-16 17:54   ` Juliusz Chroboczek
2021-07-16 18:04 ` Juliusz Chroboczek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='[Galene] Re: 0.4 tag & locked/unlocked state available?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox