From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: guix-devel@gnu.org
Subject: Updates for Go
Date: Tue, 15 Aug 2023 13:57:58 -0600 [thread overview]
Message-ID: <ubglc6$8nj$1@ciao.gmane.io> (raw)
Hey all,
Our Go ecosystem is currently in need of a lot of love.
* The Go Team
There is currently no branch for Go updates. I know Leo had tried to get
one setup at one point[0] but ran into issues. I'm unclear if they were
ever resolved, but the branch isn't there, and we need one.
There's also no one on Guix's Go team. I've created a patch to add
myself[1], although my availability has historically been very
intermittent. Please consider joining since the Go ecosystem contains
some pretty critical packages (e.g. Docker, syncthing, etc.).
* Go Versions
Go v1.21.0 has just been released. Go's release policy[2] states that
releases are supported until two major releases have been made. We're
building everything in Go 1.17.3 by default right now which puts our Go
ecosystem at risk since our packages won't be using security fixes that
have since been released.
To help address this, I've proposed[3] a Go v1.21.0 package, but not
made it the default.
Next, we should get started on compiling everything with a supported
version of Go. It would be nice to switch the default to Go v1.21.0
since it has some nice performance improvements. To do this, we'll need
the feature branch so we can begin working on what's broken.
What do you all think? If it's just me trying to fix broken packages,
we're going to be on Go v1.17 for a long time!
[0] https://lists.gnu.org/archive/html/guix-devel/2023-01/msg00097.html
[1] https://issues.guix.gnu.org/65314
[2] https://go.dev/doc/devel/release#policy
[3] https://issues.guix.gnu.org/65317
--
Katherine
next reply other threads:[~2023-08-15 20:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 19:57 Katherine Cox-Buday [this message]
2023-08-16 17:25 ` Updates for Go Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-17 14:25 ` Katherine Cox-Buday
2023-08-17 21:54 ` Wilko Meyer
2023-08-18 1:52 ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-08-19 11:31 ` Attila Lendvai
2023-08-21 18:14 ` Katherine Cox-Buday
2023-08-21 16:10 ` Katherine Cox-Buday
2023-08-21 17:53 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-21 18:17 ` Katherine Cox-Buday
2023-08-22 9:59 ` Josselin Poiret
2023-08-22 13:14 ` Attila Lendvai
2023-08-22 14:24 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-23 16:12 ` Katherine Cox-Buday
2023-08-27 15:41 ` wolf
2023-08-28 15:18 ` Katherine Cox-Buday
2023-08-22 11:01 ` Wilko Meyer
2023-08-22 18:06 ` david larsson
2023-08-23 15:35 ` Katherine Cox-Buday
-- strict thread matches above, loose matches on Subject: below --
2023-08-26 0:29 John Kehayias
2023-08-28 15:14 ` Katherine Cox-Buday
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='ubglc6$8nj$1@ciao.gmane.io' \
--to=cox.katherine.e@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).