You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2022/12/12 10:41:38 UTC

[GitHub] [iceberg-docs] gaborkaszab commented on a diff in pull request #187: Update the how-to-release page with findings after being a release manager

gaborkaszab commented on code in PR #187:
URL: https://github.com/apache/iceberg-docs/pull/187#discussion_r1045663147


##########
landing-page/content/common/how-to-release.md:
##########
@@ -222,6 +246,12 @@ Therefore, the release candidate is passed/rejected.
 
 After the release vote has passed, you need to release the last candidate's artifacts.
 
+But note that releasing the artifacts should happen around the same time the new docs are released

Review Comment:
   I wouldn't put the section to prepare the doc PRs before the voting is finished. You might end up preparing the PRs multiple times if more RCs are needed to pass the vote. I figured the ideal place to prepare the doc PRs is after the vote has passes and we started working on finishing the release.



-- 
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@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org