Consider releasing bugfix-versions more frequently
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1.4k
- Forks
- 379
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 8
Description
There have been so 141 commits since the last release of 3.3.0 in March 2026. They fix many things around ansible 2.19, which is great, thanks!
But unfortunately, they were not released yet. (E.g. for myself, I'm waiting for https://github.com/debops/debops/commit/881942bf4ccabef7ae1a099c4bf43a428986eabf which will fix a "big red" during the first run on every new machine. Right now, I have to run ansible twice.)
It would be great therefore, if such bug fixes would be released more frequently. I could probably just use the stable-3.3 branch or a certain commit, instead of using version: 3.3.0. But tbh, I'm a fan of using tagged versions.
Contributor guide
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 by reviewing the repository's release process and the stable-3.3 branch, then inspect the changes since the 3.3.0 tag, including commit 881942bf4ccabef7ae1a099c4bf43a428986eabf. Done means establishing and documenting a more frequent bugfix-release process with a tagged version users can consume.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, infrastructure, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100