Orange-OpenSource / Orange-OpenSource/its-client
Versionning scheme and publication automation
Open
@ymorin-orange is already working on this.
Since Nov 29, 2024.
documentation
Java
Python
question
Rust
Schema
- Dominant language
- Java
- Stars
- 19
- Forks
- 12
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 3
Description
What:
- We currently have no versionning scheme for the release of the various components.
- Components are not automatically published to the corresponding "registries" (crates.io, PyPi, Mavenc central)
Expected:
- There is a clear policy about the versionning scheme. Shall we have:
- a single versionning for all components and release everything at once?
- a versionning per language, and release all components in that language at once?
- a versionning for the SDK as a whole and release a single SDK in all languages at once? If so, what about the various components (e.g. in python)?
- a versionning per component in each language?
- Once the versionning policy has been established, how do we enforce it:
- github workflows to publish?
- how to detect that comething has to be relased:
- tag fomatting scheme?
- metadata in tag commit log?
- where to publish the JSON schemas?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.