README-MAINTAINER update timestamp

Author: ilg-ul

README-MAINTAINER.md

@@ -42,7 +42,7 @@ For archiving purposes, the release is also published in a separate folder
 for each version, with the archive in the top folder and the p2 repo as
 a sub-folder
 
-- <https://download.eclipse.org/embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202210101738.zip>
+- <https://download.eclipse.org/embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202304281106.zip>
 - <https://download.eclipse.org/embed-cdt/releases/6.3.2/p2/>
 
 The official download page is
@@ -176,6 +176,8 @@ When ready, merge the `develop` branch into `master`, and push them to GitHub.
 
 Wait for the GitHub Actions CI job to confirm that the build passed.
 
+- <https://github.com/eclipse-embed-cdt/eclipse-plugins/actions>
+
 ### Trigger the Jenkins master build
 
 - go to [https://ci.eclipse.org/embed-cdt/job/build-plug-ins/](https://ci.eclipse.org/embed-cdt/job/build-plug-ins/)
@@ -261,14 +263,14 @@ In Eclipse:
 - right click: **Show Properties View**
 - in the right side, edit the **Location** field to the new release
 candidate p2 URL (like
-`https://download.eclipse.org/embed-cdt/release-candidates/6.3.2-202210101738/p2/`
+`https://download.eclipse.org/embed-cdt/release-candidates/6.3.2-202304281106/p2/`
 and press Enter
 - select all the features in the contribution, right-click and choose
 **Fix Versions**
 - select the Contribution and **Validate**
 - select the Aggregation and **Validate**
 - Save
-- commit _embedcdt: update for 6.3.2-202210101738_
+- commit _embedcdt: update for 6.3.2-202304281106_
 - _Signed-off-by: Liviu Ionescu <ilg@livius.net>_
 - _Signed-off-by: Liviu Ionescu &lt;ilg@livius.net&gt;_
 
@@ -297,7 +299,7 @@ In about 5 minutes it'll automatically rebuild the staging repo:
 
 Announce the release candidate to the **embed-cdt-dev@eclipse.org** list;
 use a subject like
-**Embed CDT v6.3.2-202210101738 release candidate**,
+**Embed CDT v6.3.2-202304281106 release candidate**,
 and pass a link to the release page, available at:
 
 - <https://projects.eclipse.org/projects/iot.embed-cdt/>
@@ -312,7 +314,7 @@ Go to the release candidate folder
 
 - [https://download.eclipse.org/embed-cdt/release-candidates/](https://download.eclipse.org/embed-cdt/release-candidates/)
 
-Copy the tag and enter it in Git, like `v6.3.2-202210101738` (with `v`).
+Copy the tag and enter it in Git, like `v6.3.2-202304281106` (with `v`).
 
 ## Publish the final release
 
@@ -366,12 +368,12 @@ In the `develop` branch, in `_posts/release`, add a new release page.
 As links for the latest two, open <https://download.eclipse.org/embed-cdt/releases/>
 and get the archive URL, like:
 
-- <https://download.eclipse.org/embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202210101738.zip>
+- <https://download.eclipse.org/embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202304281106.zip>
 
 Isolate the part starting with `/embed-cdt/...` and update the URLs to use the download redirect:
 
-- <https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202210101738.zip>
-- <https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202210101738.zip.sha>
+- <https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202304281106.zip>
+- <https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202304281106.zip.sha>
 
 Update the milestone URL.