You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@polaris.apache.org by "pingtimeout (via GitHub)" <gi...@apache.org> on 2026/01/07 18:22:21 UTC
[PR] Update release guide to reference the proposed vote e-mail [polaris]
pingtimeout opened a new pull request, #3377:
URL: https://github.com/apache/polaris/pull/3377
Now that #3150 has been merged, a VOTE e-mail is pre-generated by the third workflow so that there is less room for error. The release guide has been updated to reflect this.
There is no pre-generated Incubator vote e-mail as part of the third workflow. This is acceptable in that eventually, after graduation, that would become unnecessary. But also that it could cause confusion as there would be two proposed e-mail bodies in the third workflow. Recommendation is to let the release manager created the Incubator vote e-mail manually.
--
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-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update release guide to reference the proposed vote e-mail [polaris]
Posted by "flyrain (via GitHub)" <gi...@apache.org>.
flyrain commented on code in PR #3377:
URL: https://github.com/apache/polaris/pull/3377#discussion_r2670823082
##########
site/content/community/release-guides/semi-automated-release-guide.md:
##########
@@ -112,82 +110,39 @@ The third Github workflow to run is [`Release - 3 - Build and publish release ar
* Build the Helm chart
* Create signature and checksum for all package files
* Copy package files to Apache dist dev repository
+* Generate an e-mail to notify the community of the availability of the release candidate
This workflow must be run from an RC tag (e.g., `apache-polaris-1.3.0-incubating-rc0`). Select the tag from the `Use workflow from` dropdown in the Github Actions UI. Selecting any other reference in the Github Actions UI will result in a failure.
## Start the vote thread
-The last step for a release candidate is to create a VOTE thread on the dev mailing list.
+The last step for a release candidate is to send a VOTE thread on the dev mailing list. The run details page for the third workflow contains a ready-to-send e-mail to notify the community of the availability of the release candidate and start the vote.
-Recommended title subject:
+
Review Comment:
Nit: If we’re providing an example, a text version would be preferable, since it’s easier to copy, search, and keep up to date than a screenshot.
--
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-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update release guide to reference the proposed vote e-mail [polaris]
Posted by "pingtimeout (via GitHub)" <gi...@apache.org>.
pingtimeout commented on code in PR #3377:
URL: https://github.com/apache/polaris/pull/3377#discussion_r2671590549
##########
site/content/community/release-guides/semi-automated-release-guide.md:
##########
@@ -112,82 +110,39 @@ The third Github workflow to run is [`Release - 3 - Build and publish release ar
* Build the Helm chart
* Create signature and checksum for all package files
* Copy package files to Apache dist dev repository
+* Generate an e-mail to notify the community of the availability of the release candidate
This workflow must be run from an RC tag (e.g., `apache-polaris-1.3.0-incubating-rc0`). Select the tag from the `Use workflow from` dropdown in the Github Actions UI. Selecting any other reference in the Github Actions UI will result in a failure.
## Start the vote thread
-The last step for a release candidate is to create a VOTE thread on the dev mailing list.
+The last step for a release candidate is to send a VOTE thread on the dev mailing list. The run details page for the third workflow contains a ready-to-send e-mail to notify the community of the availability of the release candidate and start the vote.
-Recommended title subject:
+
Review Comment:
Thanks for your feedback @flyrain. To give you more context, I excluded the copy/keep up to date aspect on purpose. The example is given so that people know what to look for (as opposed to just referring to a details page with no further explanation). It is not made to be copied nor kept up to date. See this sentence in the `Overview` paragraph of the current semi-automated release guide:
> Note that all screenshots in this page are for illustration purposes only. The actual repository name, version numbers, etc. may be different.
--
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-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update release guide to reference the proposed vote e-mail [polaris]
Posted by "pingtimeout (via GitHub)" <gi...@apache.org>.
pingtimeout merged PR #3377:
URL: https://github.com/apache/polaris/pull/3377
--
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-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org