oras-project
Rust Client release planning
How is release planning done here? There are no milestones. Is there another tool used?
Working on https://github.com/oras-project/community/pull/64
Honestly, we don't have any milestone. We usually tag new releases whenever:
- a bunch of PRs with new fixes are merged into
main - a security update is done
We regularly merge the dependency bumps we get, but we fail to tag new releases unless there's something that falls into the previous categories.
Maybe we could setup some automation, runs on a monthly basis, that makes a PR for a new patch release if something changed since the last release. I've something like that done inside of another repo I maintain.
Yeah, very much on an as needed basis here as things are fairly stable. There are few other things we should work on to support new OCI spec stuff and a few other spit and polish features, but otherwise mostly dep bumps.
@flavio I wouldn't be opposed to autobumping the patch version on a regular cadence for all non-breaking dep updates
@flavio I wouldn't be opposed to autobumping the patch version on a regular cadence for all non-breaking dep updates
Good, I'll look into the other automation I mentioned and try to port it over to this repo