Orange-OpenSource / Orange-OpenSource/its-client
Document the release process in a file at the repository root (e.g. RELEASE-PROCESS.md)
Open
@fsuc is already working on this.
Since Apr 9, 2025.
documentation
- Dominant language
- Java
- Stars
- 19
- Forks
- 12
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 3
Description
- We all agree that one version for all is not suitable
- No version change in functional branches
- Version changes have to be made in dedicated branches
- When merging into master, check the diff to identify if any version has changed.
If any, build and publish the new package at the new version; and a new git tag is createdlanguage.module-version - If at publish a package at this version already exists, the pipeline job must fail
- Example are not published
- Semantic tags (created manually): YYYYmmdd.HHMM-purpose
E.g. 20241120.1212-Demo-5GLab - Version should follow the X.Y.Z form where X is major, Y minor, and Z fix (see https://semver.org/)
- Create a new webpage (gh-pages)
- Rust packages are published on crates.io; and documentation on docs.rs
- Python packages are published on pypy.org; and documentation on readthedocs.com
- Java packages are published on ?
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.