We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Which version scheme do we want to use?
Options:
1.2.3
2023.1
Aachen
1
Related issues:
#130 decided that versions are only about identity and relation, nothing more implied.
#58 decided that M3 and serialization format share a version, i.e. an M3 and the corresponding serialization format always have the same version.
The text was updated successfully, but these errors were encountered:
Decision on 2023-09-19 in Slack: Time-based
This also means we change the format of serializationFormatVersion field in serialization.
serializationFormatVersion
Sorry, something went wrong.
adjusted version to new format, name
d5caaa9
renamed serializationFormatVersion -> serializationFormatRelease renamed LionWeb version -> LionWeb release changed JSON field constraints relates to #165, #172
Should close this
No branches or pull requests
Which version scheme do we want to use?
Options:
1.2.3
2023.1
(Year.incremented integer starting at 1)Aachen
1
Related issues:
#130 decided that versions are only about identity and relation, nothing more implied.
#58 decided that M3 and serialization format share a version, i.e. an M3 and the corresponding serialization format always have the same version.
The text was updated successfully, but these errors were encountered: