From 5f75f473b509e4ce3d40f3ee4af52066745643e9 Mon Sep 17 00:00:00 2001 From: Stewart X Addison <6487691+sxa@users.noreply.github.com> Date: Wed, 31 Jan 2024 20:05:38 +0000 Subject: [PATCH] doc: Add EclipseMirror information to RELEASING.md (#3365) * doc: Add EclipseMirror information to RELEASING.md Signed-off-by: Stewart X Addison * Updates following review Signed-off-by: Stewart X Addison * Add : Signed-off-by: Stewart X Addison --------- Signed-off-by: Stewart X Addison --- RELEASING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 7391db0a0..07cbf1757 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -315,11 +315,12 @@ Once the PRs to change those files have been merged, the [adoptium-packages-linu 4. **[Docker Hub]** The information on updating the Adoptium official dockerhub repository is at at the moment you cannot do this until all Linux architectures and windows64 are published for the appropriate version -5. Publicise the Temurin release +5. Once everything has been published to GitHub, use the [EclipseMirror](https://ci.eclipse.org/temurin-compliance/job/EclipseMirror/) job to mirror the artifacts to our Eclipse server for backup purposes. Note that this will need to be done by a team member in the temurin-compliance project (Run once for each of the releases) + +6. Publicise the Temurin release: - Via slack on the Adoptium #release channel - Find someone with the appropriate authority (Carmen, George, Martijn, Shelley, Stewart, Tim) to post a tweet about the new release from the Adoptium twitter account -- Also run the EclipseMirror job in the Eclipse jenkins instance to create a backup of the release from GitHub onto the Eclipse servers. ### Post Release Tasks