Add previous supported ServerAPI definitions #327
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add previous versions of the Server API server definition to the project, and expose the bindings in separate namespaces, with names like
v2024r2
. This seems to work as expected, but there are a couple of points for discussion:v2025r2
. This has the advantage of keeping things nice and easy as we transition from 25r2 development to hardening and release, but it maybe makes it look likev2025r2
is as stable as the other packages.latest
. Maybe this is ok? If we wanted to add it, we'd probably need to flag a certain definition aslatest
, and make a change to the template to include a special section in the top-level__init__,py
for this package. It would need to go last in pom.xml though, to make sure it didn't get clobbered by subsequent builds which 'aren't' latest. Either that, or we'd need some clever runtime definitions to figure out which one is 'latest'.