From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Guix minor version update?
Date: Tue, 21 Jan 2020 14:32:00 +0100 [thread overview]
Message-ID: <CAJ3okZ1dz6dQZ04wDbxCKLbuhWfQ9wmN8DbjydwVZ_g5cB3qiQ@mail.gmail.com> (raw)
Dear,
Currently, the proposed Guix to install is v1.0.1. This very version
has some "bugs" [1] fixed since then [2]. But it is not convenient
when using with Docker [3].
Why not update the minor version to v1.1?
Then, I propose to update this minor version:
- each time core-updates or staging is merged
- each time the bootstrapping toolchain is updated
- each time major archives (Bioconductor) is updated
- each time CLI is improved (time-machine, etc.)
Ludo "disagrees" [4], kind of. ;-)
<<
I guess semver doesn’t apply to Guix taken as a whole, so version
numbers should be chosen to suggest how “different” the new release is.
That’s pretty subjective, though.
>>
Let collect some ideas. :-)
Even if version is not really meaningful when speaking about Guix
because rolling etc. I find useful to bump the minor version more
often, IMHO, for 3 reasons:
1. Changing the (minor) version attracts interest and increases visibility.
2. It helps people --mainly HPC sysadmins-- to better trust "Guix
rocks!" because jumping from version to version fits more what they
know.
3. It eases to navigate through all the packages and their version update.
What people think?
All the best,
simon
[1] https://lists.gnu.org/archive/html/guix-devel/2019-11/msg00540.html
[2] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=c20ba18304ee63f01895f092bb51bc2a9ce3303b
[3] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39195
[4] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39195#25
next reply other threads:[~2020-01-21 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 13:32 zimoun [this message]
2020-01-21 15:37 ` Guix minor version update? Pierre Neidhardt
2020-01-21 17:43 ` Julien Lepiller
2020-01-22 1:35 ` Bengt Richter
2020-01-23 16:28 ` Ludovic Courtès
2020-01-24 16:31 ` Jonathan Frederickson
2020-01-24 17:08 ` zimoun
2020-01-23 15:42 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ1dz6dQZ04wDbxCKLbuhWfQ9wmN8DbjydwVZ_g5cB3qiQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).