Thanks for starting the discussion! To add a bit more color, we should at least add a test job to make sure the release script can produce the packages correctly. Today it's kind of being manually tested by the release manager each time, which slows down the release process. It's better if we can automate it entirely, so that making a release is a simple click by authorized people.
On Thu, May 9, 2024 at 9:48 PM Nimrod Ofek <ofek.nim...@gmail.com> wrote: > Following the conversation started with Spark 4.0.0 release, this is a > thread to discuss improvements to our release processes. > > I'll Start by raising some questions that probably should have answers to > start the discussion: > > > 1. What is currently running in GitHub Actions? > 2. Who currently has permissions for Github actions? Is there a > specific owner for that today or a different volunteer each time? > 3. What are the current limits of GitHub Actions, who set them - and > what is the process to change those (if possible at all, but I presume not > all Apache projects have the same limits)? > 4. What versions should we support as an output for the build? > 5. Where should the artifacts be stored? > 6. What should be the output? only tar or also a docker image > published somewhere? > 7. Do we want to have a release on fixed dates or a manual release > upon request? > 8. Who should be permitted to sign a version - and what is the process > for that? > > > Thanks! > Nimrod >
