-
-
Notifications
You must be signed in to change notification settings - Fork 349
add a 'v' to the version number in the meta-schema uri #1634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I can see some merits in releasing the next version as v1, implying that up until now the releases were not at the same level of stability, but I still don't understand the intent behind making a secondary number be the year. It (like our previous release numbers) artificially dates the release (draft2020-12 looks old simply because 2020 was five years ago), but also artificially places a limit on one release per year. If we wanted to do a second release within the same year, does that mean we'd be forced to increment the first component of the version, even if it otherwise did not merit it?
What kind of change does this PR introduce?
General update
Issue & Discussion References
None
Summary
I saw this in Slack in a conversation between @karenetheridge and @jdesrosiers. I'm not sure who came up with it, but I think it addresses @karenetheridge's concerns that the 1/2025 looks like a date.
Does this PR introduce a breaking change?
No. It's already broken.