-
Notifications
You must be signed in to change notification settings - Fork 630
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
Define a regular crates-io release cycle #2936
Comments
Chatted with @Dirbaio, there's loose interest, before we can do that, we need to make the following docs/process things happen:
|
Crate Inventory$ git log | head -n 1
commit b33ef0d7dd4eb9124626ca5242cab57906b3007c
$ find . | rg 'Cargo.toml$' | rg -v '/examples/' | rg -v '/tests/'
./embassy-net-ppp/Cargo.toml
./embassy-usb-driver/Cargo.toml
./embassy-stm32/Cargo.toml
./embassy-net-esp-hosted/Cargo.toml
./cyw43-pio/Cargo.toml
./embassy-time/Cargo.toml
./embassy-executor/Cargo.toml
./embassy-time-queue-driver/Cargo.toml
./embassy-boot-nrf/Cargo.toml
./embassy-net-driver-channel/Cargo.toml
./embassy-rp/Cargo.toml
./embassy-hal-internal/Cargo.toml
./embassy-sync/Cargo.toml
./embassy-usb/Cargo.toml
./embassy-nrf/Cargo.toml
./embassy-futures/Cargo.toml
./embassy-net-wiznet/Cargo.toml
./embassy-usb-logger/Cargo.toml
./embassy-usb-synopsys-otg/Cargo.toml
./embassy-net-driver/Cargo.toml
./embassy-net-tuntap/Cargo.toml
./embassy-usb-dfu/Cargo.toml
./embassy-boot-rp/Cargo.toml
./embassy-net-adin1110/Cargo.toml
./embassy-boot/Cargo.toml
./embassy-net-enc28j60/Cargo.toml
./embassy-time-driver/Cargo.toml
./embassy-embedded-hal/Cargo.toml
./embassy-boot-stm32/Cargo.toml
./cyw43/Cargo.toml
./embassy-net/Cargo.toml
./embassy-executor-macros/Cargo.toml
./embassy-stm32-wpan/Cargo.toml Still todo, figuring out the inverted dep tree order. |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be good to commit to a more regular crates-io release cycle, in order to get more people away from patches when possible.
It might be good to set up some regular cadence, like every week or two, if there have been any changes.
I don't think we necessarily need to commit to a more stringent stability guarantee, it could be a (breaking) point release every time for the foreseeable future.
The text was updated successfully, but these errors were encountered: