Hi,
when I started up a shell with a go, I noticed that the version I got
was a big weird, 1.26rc1 to be precise. According to Efraim that is
fine, but I do not understand why (I am not disputing, just looking to
understand). Should not the package one gets from
guix shell go
not be the latest, but *stable* version (so currently go-1.25)?
Especially since we are getting close to a release, it feels weird to
have go default to a release candidate.
I guess I have two questions:
1. Why not have go-next instead if 1.26 is needed for some reason?
2. What are rules for when it is fine to update package to release
candidate instead of waiting for the final version?
Thanks,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
