On Wed, Feb 9, 2022 at 7:32 AM Julian Foad <julianf...@apache.org> wrote: > > Mark Phippard wrote: > > [...] Or are you suggesting > > the vote in STATUS essentially "counts" as the approval we need? > > That, plus automating the mechanical parts, forms the essence of it. > These two things (the current double voting (once to apply the patch and > again to release it) and the non-automated automatable process) seem to > be the two main burdens we could reduce. > > +1 to your point about not making releases that just contain a trivial > patch, so we do want some batching. How to combine "some batching" with > the above, I wonder?
Just thinking out loud .... What if the "patch release process" just involved a committer pushing a tag that included the version bump and CHANGES update and then the production of the release artifacts was automated off the tag creation process? This would allow a release to include more than one fix if desired. I do wonder about the voting though. The Apache process requires us to have a release vote. I am not sure we can count the STATUS votes. It would certainly be something to key in on for discussion purposes. I have long thought that committers building and testing the releases was a waste of our limited capacity. It seems like the sort of thing that could be automated with a few bots for different OS that can build a release from the tarball and run the tests. Realizing that building this automation also requires people to do it. Mark
