While votes are usually focused on code modifications [1] and package releases [2], I think it would be helpful to have a formal vote on improving the release process. The discussion thread received some +1s, but I would like to make sure this is handled as a formal vote.
This vote is based on the discussion: ``` [DISCUSS] Improving Release Process & Voting ``` For any questions, please reply in the discussion thread. --- TL;DR This is a summary of what is being voted on: 1. Use GitHub Actions (GHA) to create a draft release. * Includes automatic signing and checksum creation. 2. Automatically upload artifacts to Apache Trusted Release (ATR) for staging. 3. Use Apache Trusted Releases (ATR) for: * Creating a vote * Submitting a vote * Finalizing a vote 4. Use GHA to publish to the npmjs registry. ***** If you want to read the full release guideline, here is a gist: https://gist.github.com/erisu/c45a04c850ef15fc69032e372fa6ec00 The guideline in the gist may be updated during the implementation phase and will be published on the official website once the implementation has been completed. ***** I vote +1 [1] https://apache.org/foundation/voting.html#votes-on-code-modification [2] https://apache.org/foundation/voting.html#ReleaseVotes
