openwisp / openwisp/openwisp-utils
[feature] Periodic automatic bugfix releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 93
- Forks
- 104
- Avg merge
- 14h 10m
- Merged PRs (30d)
- 22
Description
Requires more discussion and research.
Follow up of the efforts to make the release process easier and free up the time of maintainers (#496), related to #501, #502.
Depends on #520, #522.
I think it would be useful to write a github action that automatically publishes bug fixes release for us at the end of each month, if there's any bugfix release available in the latest stable branch.
I think the right way would be to execute the releaser tool on the latest stable branch, we'll need to issue a new github token for this set as organization secret, then we'll need to enable the github action in all the repos we maintain.
The output should be a pull request with the version bump and the change log (the releaser tool should already be able to do this, but we may need to allow to do it non interactively).
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 reading the related issues #496, #501, #502, #520, and #522, then inspect the existing releaser tool and its non-interactive capabilities. Define how the GitHub Action should run against the latest stable branch, use the organization secret, and create a version-bump and changelog pull request across maintained repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100