@@ -98,10 +98,18 @@ Here you should use the release tag.
98
98
You can find the list of people with such access in the team shared folder.</span > \
99
99
To do that:
100
100
* log on to the [ Sonatype Central Portal -- Namespaces] ( https://central.sonatype.com/publishing/namespaces ) .
101
- * Select the "Deployments" tab.
102
- * Check the files staged there, compare to a previous public release in Maven Central
101
+ * Select the ** Deployments** tab.
102
+ ![ image] ( mcp-deployments.png )
103
+ * Check the files staged there (` icu4j-charset ` is similar):
104
+ ![ image] ( mcp-deployment-files.png )
105
+ * Compare to a previous public release in Maven Central
103
106
(for example [ ICU4J 77.1] ( https://repo1.maven.org/maven2/com/ibm/icu/icu4j/77.1/ )
104
107
and [ ICU4J Charset 77.1] ( https://repo1.maven.org/maven2/com/ibm/icu/icu4j-charset/77.1/ ) ) \
105
- For now sanity check is probably: make sure there are no errors / warnings, make sure the new staged files match the ones in the 2 links above.
106
- * Once you confirm the contents, approve it.
107
- * <span style =" color :red " ><b >TODO: update this doc with screenshot(s) once we have a release staged.</b ><span >
108
+ And do a sanity check:
109
+ * make sure there are no errors / warnings
110
+ * the timestamps look reasonable
111
+ (close to the time when the ICU4J publish GitHub action finished),
112
+ * the version is the one you expect to release
113
+ * the file sizes didn't drastically change from the previous release
114
+ * Once you confirm that everything looks reasonable, approve the deployment
115
+ (click ** Publish** ).
0 commit comments