DragonFly 3.4 is branched – as a release candidate, with the current target for 3.4.0 release as the weekend of April 13-14. See the tagging commit note for a list of all the commit messages.
Note that in previous releases, we tagged “x.y.0” on branch, and “x.y.1” on release. I’m now tagging “x.y.0rc” for the release candidate at branch time, and we’ll tag with a more normal (to my ears) “x.y.0” for the release.
If you build a 3.4.0rc image right now, you’ll get an older quarterly release of pkgsrc. That’ll be changed tomorrow as the DragonFly pkgsrc git source is updated and I change where 3.4’s /usr/Makefile points.
That’s going to end up with x.y.0rc > x.y.0 when doing a lexical sort, isn’t it? Probably not that big a deal but I’m living the xkcd comic re: ISO 8601 dates.
As the one person who comes back every 3 to 24 months maybe I’ll put a word in for affirmative metadata (like -RELEASE) as the equivalent of surgical “THIS LEG / NO! THE OTHER LEG!” markings re: being confident that I’ve actually grabbed the right things, but that’s probably only happened in DragonFly when I’ve overlooked the .0 vs .1 thing, so the bikeshed is a lovely color this year.
I can see how the sorting wouldn’t be great – but why would we keep the release candidate image around? Can’t sort wrong if it’s deleted.