Since this project is still in its early stages, it might be useful to have a discussion about versioning.
From my perspective, based on the current README, it should be clear:
- Which OSI version is installed when running
pip install osi-python
- Whether the package supports only the latest OSI version or also older ones
- How package updates/versions map to OSI versions
A minimal approach could be to always target the latest OSI release. In this case, bugs in osi-python may not be officially backported to older versions. We could start with this approach but already introduce a versioning scheme that indicates the standard version being used. For example: osi-python==1.2.3+std3.7.
This issue doesn’t necessarily propose immediate changes, but rather documents the topic so we can briefly discuss it in an upcoming meeting.
Since this project is still in its early stages, it might be useful to have a discussion about versioning.
From my perspective, based on the current README, it should be clear:
pip install osi-pythonA minimal approach could be to always target the latest OSI release. In this case, bugs in
osi-pythonmay not be officially backported to older versions. We could start with this approach but already introduce a versioning scheme that indicates the standard version being used. For example:osi-python==1.2.3+std3.7.This issue doesn’t necessarily propose immediate changes, but rather documents the topic so we can briefly discuss it in an upcoming meeting.