-
Notifications
You must be signed in to change notification settings - Fork 42
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
pypi release for 0.4 #68
Comments
Agree. A couple of notes
|
No, not at all. For some libraries (Web Editor, JS, R) this is the case at the moment for minor versions (e.g. JS client 0.4.0 supported API 0.4.0/1/2), but that's more a somewhat useful coincidence than a planned behaviour. So feel free to release it with whatever version you'd like, but according to the guidelines for the project, SemVer should be followed. See point 9.
I don't think there is an account yet as there's no package yet.
Not a big deal, I think. We should release only once it's "ready" and I think the Python client needs some more work beforehand? |
Indeed, some more work is needed before it can be considered "ready". |
You could also release something like x.x.x-beta.1, which is what I do for the JS client, Web Editor etc. |
Closing: multiple pypi releases have been published already, and we regularly create new releases. |
…tency The "round up" end_date feature as originally proposed turned out to conflict too much with existing behavior and openEO spec. Still, the idea can still be provided through single string `extent`: "2022" -> ("2022-01-01", "2023-01-01")
…tency The "round up" end_date feature as originally proposed turned out to conflict too much with existing behavior and openEO spec. Still, the idea can still be provided through single string `extent`: "2022" -> ("2022-01-01", "2023-01-01")
Could we get a pypi release for 0.4 once it is ready, please? This would allow us to use this library as a dependency for other projects, e.g. the backend-result-validator. See Open-EO/openeo-result-validation-engine#43
The text was updated successfully, but these errors were encountered: