Since PVP doesn't have explicit support for prereleases, there are a few techniques that have been practiced in the community, e.g. GHC:
This allows PVP compliant update once the real 9.4.1 is released.
I don't think the spec should enforce any of that, but what if we provide this as a non-enforced practice recommendation.
VSCode has something similar, where major.EVEN_NUMBER.patch marks a release and major.ODD_NUMBER.patch marks a pre-release: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#prerelease-extensions
So in our terms, X.Y.EVEN_NUMBER.<date-number> is the pre-release for X.Y.ODD_NUMBER or somesuch?
Since PVP doesn't have explicit support for prereleases, there are a few techniques that have been practiced in the community, e.g. GHC:
9.4.0.20220501This allows PVP compliant update once the real
9.4.1is released.I don't think the spec should enforce any of that, but what if we provide this as a non-enforced practice recommendation.
VSCode has something similar, where
major.EVEN_NUMBER.patchmarks a release andmajor.ODD_NUMBER.patchmarks a pre-release: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#prerelease-extensionsSo in our terms,
X.Y.EVEN_NUMBER.<date-number>is the pre-release forX.Y.ODD_NUMBERor somesuch?