-
Notifications
You must be signed in to change notification settings - Fork 102
Description
As an instructor teaching a university course involving Julia-based practicals, I'm not sure which of the existing juliaup
channels I should recommend to my students to use:
release
may at times catapult them onto a very fresh release (patch level 1.x.0, just a few days old, where the ecosystem has not yet had time to discover and iron out new incompatibilities and glitches).lts
may at times lead to a very old release, lagging years behind the state of the art.
Students in courses are usually first-time Julia users without any experience of making such judgement calls themselves. They deserve the smoothest possible experience as new Julia users, and neither release
nor lts
are in practice ideal for that.
I would like to see a mature
channel that tracks release
with a cautious/conservative delay, such that it roughly
- updates to a new “minor” release version only once per year, during the summer break (late July / early August), well before the start of the next academic year in the northern hemisphere
- avoids updating to new “minor” 1.x releases until issues have calmed down (e.g., there hasn't been a significant new patch release for at least ~5 weeks)
- delays updating to new patch releases for ~2–3 weeks, to leave some time for monitoring of new issues introduced by those
In case the current lts
release is reasonably recent, mature
might also linger on that until the end of the academic year.
(There might of course also be demand for a mature-south
channel more in sync with the academic years of schools in the southern hemisphere.)
Managing such a mature
channel is of course a bit more involved than the other channels, as it involves making judgement calls and liaising with various release managers and triaging teams in the Julia community, to get a sense of how “mature” a minor or a patch release has become.