Skip to content

Version scheme for LionWeb? #165

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

Closed
enikao opened this issue Sep 15, 2023 · 2 comments
Closed

Version scheme for LionWeb? #165

enikao opened this issue Sep 15, 2023 · 2 comments

Comments

@enikao
Copy link
Contributor

enikao commented Sep 15, 2023

Which version scheme do we want to use?

Options:

  1. SemVer 1.2.3
  2. Time-based (tags) —> 2023.1 (Year.incremented integer starting at 1)
    • Pro
      • Gives some indication about order and time
    • Con
      • Might feel outdated, even if “just” stable
  3. City names Aachen
  4. Single integer 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.

@enikao
Copy link
Contributor Author

enikao commented Sep 19, 2023

Decision on 2023-09-19 in Slack: Time-based

This also means we change the format of serializationFormatVersion field in serialization.

enikao pushed a commit that referenced this issue Sep 25, 2023
renamed serializationFormatVersion -> serializationFormatRelease
renamed LionWeb version -> LionWeb release
changed JSON field constraints

relates to #165, #172
@joswarmer
Copy link
Contributor

Should close this

@enikao enikao closed this as completed Jan 26, 2024
@enikao enikao added the versions label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants