From: Juliusz Chroboczek <jch@irif.fr>
To: Sebastien Binet <binet@cern.ch>
Cc: galene-list <galene@lists.galene.org>
Subject: [Galene] Re: Galene tags & webserver API
Date: Mon, 29 Apr 2024 20:54:19 +0200 (GMT+02:00) [thread overview]
Message-ID: <441d3dfa-e5a8-4e62-8dfc-cd8656846aa2@irif.fr> (raw)
In-Reply-To: <D0WM0N7L8TT7.1M3XLXOERW3YB@cern.ch>
Hi,
> 1) why does the Galene project tags releases with "galene-X.Y.Z"
> instead of the Go-modules compatible "vX.Y.Z" ?
> using "vX.Y.Z" would enable nicer-looking 'require' sections in
> projects using galene.
Go versions obey semver semantics. Galene internals, on the other hand,
are not compatible between versions
Hence, you cannot depend on a major version of Galene, you need to depend
on a precise got hash.
In order to keep people from assuming semver semantics, I'm deliberately
using an incompatible versioning scheme.
> 2) would you be ok with PRs reducing the amount of global variables in
> the webserver package?
Difficult to say without seeing the PR, but I don't have an objection in
principle.
-- Juliusz
prev parent reply other threads:[~2024-04-29 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 12:36 [Galene] " Sebastien Binet
2024-04-29 18:54 ` Juliusz Chroboczek [this message]
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=441d3dfa-e5a8-4e62-8dfc-cd8656846aa2@irif.fr \
--to=jch@irif.fr \
--cc=binet@cern.ch \
--cc=galene@lists.galene.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox