pingtimeout commented on issue #2017: URL: https://github.com/apache/polaris/issues/2017#issuecomment-3150612383
I have indeed started the work on release automation. However there are gaps between the current implementation and what is requested as part of this issue. See below > 1. Automated testing as part of the release verification process > 2. Failing to publish the release if verification process fails > 3. The ability to redraft a release if **verification fails** (or voting fails) This part has been discussed and we decided not to include it during the release automation. The rationale is that any release must be cut from a commit that has been validated by Github CI. I.e. for a given SHA, we verify that no Github check has failed, giving us the assurance that all tests (unit and integration) have successfully run against that SHA. > 3. The ability to redraft a release if (verification fails or) **voting fails** The scripts include the possibility to recreate a release branch and a release tag. That being said, if a vote fails for a given release candidate, I believe that we should use a different RC number for the subsequent attempt. This means we should not really need to redraft a release. > Drafting a release notifies the dev mailing list for a vote I recall some discussions about possible restriction on e-mail automation. But I could not find an official ASF page that forbids them for project releases. The current scripts do not include those. But, should this be allowed, we could include it as part of a Github workflow. > The releases should not be built upon a user’s hardware, but only on “trusted instances” (for example, GitHub). > A user can verify that the code was built on a “trusted instance”. Currently, the scripts can only be run on a user's hardware. There is no Github workflow yet. This is intended as I think we will have a couple of iterations before the release process is completely ironed out and ready for full automation. I suspect we will transition to a Github Workflow based release system in a couple of months. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@polaris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
