config: boot defaults from CURRENT rather than STABLE
Which version a build uses when nothing has selected one was STABLE, the
most recently released schema. That is the wrong answer for it. A build
defaults to the schema it was written around, and between releases that
is the one under development, not the one the last release shipped.
Booting from STABLE makes every default a development branch changes
inert unless a config file opts in, which is backwards: the departures
are the point of a development branch.
Boot from CURRENT instead. This needs no notion of whether the build is
a tagged release: at a release the two constants name the same schema, so
a release build boots the released defaults by the same rule, and they
part company again only as development resumes.
Nothing changes today, because the two schemas are still identical. It
matters from the first key version 2 adds, and selecting version 1 keeps
working because a version resolves through its chain.
projects / bees / commit