Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: "Michael Ströder" <michael@stroeder.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: tagging and semver
Date: Mon, 19 Jul 2021 13:10:21 +0200	[thread overview]
Message-ID: <87bl6ymuea.wl-jch@irif.fr> (raw)
In-Reply-To: <659b6c8a-1b32-78ce-b31b-bb681bee69c1@stroeder.com>

>>> would be a release newer than 0.3.0 and not a 0.4.0 pre-release.

>> Do you have any better suggestions?

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

It's convenient.  If you have some time, I'd like us to design a tagging
scheme that allows me to tag pre-release versions without making
packagers' lives uselessly complicated.

Galène does not use semantic versioning, which is the reason why my tags
are of the form « galene-0.3.4 » rather than « v0.3.4 » (the latter would
imply semver).  Callling pre-release versions « galene-0.3.99.x » is the
logical thing for me, since it preserves the ordering on release
numbers -- Debian-style « 0.4.0pre3 » uses a negative digit, which I find
confusing.

  https://en.wikipedia.org/wiki/Quater-imaginary_base

Given that Galène does not use semantic versioning, do I cause actual
problems if I create a tag « galene-0.3.99.0 » ?

-- Juliusz

  reply	other threads:[~2021-07-19 11:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 13:11 [Galene] 0.4 tag & locked/unlocked state available? 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
2021-07-19 11:10         ` Juliusz Chroboczek [this message]
2021-07-16 14:16   ` 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

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

  git send-email \
    --in-reply-to=87bl6ymuea.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=galene@lists.galene.org \
    --cc=michael@stroeder.com \
    --subject='[Galene] Re: tagging and semver' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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