Background
With the large scale of the projects, it can be difficult to find time to manage releases and PRs that come in, in a timely manner. This issue summarizes some ideas that would decrease maintainer toil around our every day release process.
Auto-release buildpacks
Since we don't have complicated versioning logic in the buildpacks, I think we should automatically publish the drafted implementation buildpack releases every week, on a schedule. Then, the main work needed by maintainers would be releasing the language family buildpacks, which is relatively straightforward and quick in comparison to releasing the implementation buildpacks
Auto-label all scripts/workflow change PRs
We auto-label some of our automated PRs, but not all. When this functionality was introduced in #360, we erred on the conservative side. Since then, I haven't observed any reason not to add the rest of our scripts/workflows to our patch file list, and let those PRs get auto-merged.
Improve auto-approval functionality
This is a useful workflow to have, but it often fails with unhelpful errors. We should look into streamlining this workflow, and see if we can increase its success rate
Keep Golang up-to-date automatically
This is a follow on from https://github.com/orgs/paketo-buildpacks/discussions/283, which I believe would be helpful
Questions/Other ideas?
If you have an argument against any of these proposals, or you'd like to add anything, feel free to comment.
Background
With the large scale of the projects, it can be difficult to find time to manage releases and PRs that come in, in a timely manner. This issue summarizes some ideas that would decrease maintainer toil around our every day release process.
Auto-release buildpacks
Since we don't have complicated versioning logic in the buildpacks, I think we should automatically publish the drafted implementation buildpack releases every week, on a schedule. Then, the main work needed by maintainers would be releasing the language family buildpacks, which is relatively straightforward and quick in comparison to releasing the implementation buildpacks
Auto-label all scripts/workflow change PRs
We auto-label some of our automated PRs, but not all. When this functionality was introduced in #360, we erred on the conservative side. Since then, I haven't observed any reason not to add the rest of our scripts/workflows to our patch file list, and let those PRs get auto-merged.
Improve auto-approval functionality
This is a useful workflow to have, but it often fails with unhelpful errors. We should look into streamlining this workflow, and see if we can increase its success rate
Keep Golang up-to-date automatically
This is a follow on from https://github.com/orgs/paketo-buildpacks/discussions/283, which I believe would be helpful
Questions/Other ideas?
If you have an argument against any of these proposals, or you'd like to add anything, feel free to comment.