Actually, the release candidate is the ‘b’ release in Greg’s parlance, which
usually exists for a very brief time. If you look at the GitHub releases, we
did make a 4.2.b.0, followed a week later by the official 4.2 release. It’s my
understanding the HEAD is considered alpha code until right bef
It occurs to me that what we are calling a "release," the rest of the world
has taken to calling a "release candidate" -- the version that is almost
complete, but still has a couple of annoying bugs hiding that users
identify as soon as they put it into service. Perhaps this would be a
convention w
