vy commented on code in PR #269:
URL: https://github.com/apache/logging-parent/pull/269#discussion_r1802992052
##########
src/site/antora/modules/ROOT/pages/release-instructions-project.adoc:
##########
@@ -91,7 +91,21 @@ You can iterate on the `release/7.8.0` branch to perfect it.
.. {site-url-staging}-7.8.0[The release staging website] is deployed using the
freshly populated `release/7.8.0-site-stg-out` branch
+
-If not, commit necessary fixes, push, and repeat.
+If not, commit the necessary fixes, push, and repeat.
+
+[#verify-release]
+== Verify the release
+
+Once the release is staged, the Release Manager should:
+
+. Follow the xref:release-review-instructions.adoc[] to verify the integrity
of the release.
+. Some projects have additional integration tests that need to run on the
release candidate artifacts:
+
+`logging-log4j2`::
++
+Run the
+https://github.com/apache/logging-log4j-samples/actions/workflows/integration-test.yaml[integration-test.yaml]
+workflow using the appropriate version number and URL of the _Staging
Repository_ as parameters.
Review Comment:
This really sounds like a step a machine should be doing. We can actually
trigger an external workflow... But I guess it won't be trivial. Let RM click
around for the time being...
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
