release python client
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 34
- Forks
- 5
- Avg merge
- 2m
- Merged PRs (30d)
- 5
Description
To properly pin protocol versions in downstream projects.
- release the current client (e.g. as of 22feaa7) as 0.6.3 and migrate the downstream users
- release the new client together with and as 0.7.0
- keep python client releases in semver-sync from then on
https://github.com/quartiq/stabilizer/issues/661
https://github.com/quartiq/booster/issues/272
https://github.com/quartiq/thermostat-eem/issues/86
thermostat-mqtt
stabilizer-fls
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.
Research direction
Start with the client state at commit 22feaa7 and review the linked stabilizer, booster, and thermostat-eem issues plus the listed downstream users. Release the current client as 0.6.3, release the new client as 0.7.0, migrate downstream users, and keep later Python client releases semver-synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100