Description
Modified by dietmarw on 2 Dec 2015 10:08 UTC
We identified several potential “levels” of semantics. The first level was the idea that all libraries must use semantic versions syntax. This would have the basic benefit that it would address issues about how to express things like pre-release versions. It also provides a basis for defining ordering as well.
This MCP is about how to deal with semantics of version numbers. By this we
mean conclusions that could be drawn about compatibility between different
versions (e.g., something that uses 3.2.1 should be able to use 3.2.2). One of the topics that come up was the idea of bugs and bug fixes. It might be that API compatibility may be present, but that the actual implementations have issues.
Based on this, it was felt that the uses annotation was still useful because it allows a level of explicit dependencies. For this reason it was felt that library developers should be able to utilize semantic version compatibility but also to explicitly override it.
Document location
Current members of the working group
- Henrik Tidefelt
- Hans Olsson
Modified by dietmarw on 18 Sep 2015 07:56 UTC
We identified several potential “levels” of semantics. The first level was the idea that all libraries must use semantic versions syntax. This would have the basic benefit that it would address issues about how to express things like pre-release versions. It also provides a basis for defining ordering as well.
This MCP is about how to deal with semantics of version numbers. By this we
mean conclusions that could be drawn about compatibility between different
versions (e.g., something that uses 3.2.1 should be able to use 3.2.2). One of the topics that come up was the idea of bugs and bug fixes. It might be that API compatibility may be present, but that the actual implementations have issues.
Based on this, it was felt that the uses annotation was still useful because it allows a level of explicit dependencies. For this reason it was felt that library developers should be able to utilize semantic version compatibility but also to explicitly override it.
Document location
Current members of the working group
- Henrik Tidefelt
- Hans Olsson
- Dietmar Winkler
Reported by mtiller on 9 Jun 2015 14:35 UTC
We identified several potential “levels” of semantics. The first level was the idea that all libraries must use semantic versions syntax. This would have the basic benefit that it would address issues about how to express things like pre-release versions. It also provides a basis for defining ordering as well.
This MCP is about how to deal with semantics of version numbers. By this we
mean conclusions that could be drawn about compatibility between different
versions (e.g., something that uses 3.2.1 should be able to use 3.2.2). One of the topics that come up was the idea of bugs and bug fixes. It might be that API compatibility may be present, but that the actual implementations have issues.
Based on this, it was felt that the uses annotation was still useful because it allows a level of explicit dependencies. For this reason it was felt that library developers should be able to utilize semantic version compatibility but also to explicitly override it.
Document location
Migrated-From: https://trac.modelica.org/Modelica/ticket/1728