Prepare repo for 2024-03 M3

Part of #116

RELEASING.md

@@ -74,7 +74,8 @@ This checklist is only used once per release cycle. Scroll down for the per-mile
     - `No digest algorithm is available to verify download` is OK to ignore when the bundles are the ones generated by the EPP build itself (such as `org.eclipse.epp.package.common.feature` or `epp.package.cpp.executable.gtk.linux.aarch64`)
     - Other warnings may be fine as well, as of the writing of this note there are 206 warnings in the build.
   - If warnings about signings occur that leave the dmg unsigned and the build does not fail, please reopen [Bug 567916](https://bugs.eclipse.org/bugs/show_bug.cgi?id=567916)
-- [ ] Run the [Notarize MacOSX Downloads](https://ci.eclipse.org/packaging/job/notarize-downloads/) CI job to notarize DMG packages on download.eclipse.org. _This can be done after promotion if time is tight or the notarization fails repeatedly. See [Bug 571669](https://bugs.eclipse.org/bugs/show_bug.cgi?id=571669) for an example of failures._ - [ ] Check the build script output to make sure that the curl calls were successful (e.g. no `curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2) ` messages) - If there is an error like the above the .dmg file that is copied to download.eclipse.org is corrupt. Run [notarize-prepare-to-redo](https://ci.eclipse.org/packaging/job/notarize-prepare-to-redo/) to rename the -signed file back to -tonotarize and then re-run the [notarize job](https://ci.eclipse.org/packaging/job/notarize-downloads/)
+- [ ] Run the [Notarize MacOSX Downloads](https://ci.eclipse.org/packaging/job/notarize-downloads/) CI job to notarize DMG packages on download.eclipse.org. _This can be done after promotion if time is tight or the notarization fails repeatedly. See [Bug 571669](https://bugs.eclipse.org/bugs/show_bug.cgi?id=571669) for an example of failures._
+- [ ] Check the build script output to make sure that the curl calls were successful (e.g. no `curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2) ` messages) - If there is an error like the above the .dmg file that is copied to download.eclipse.org is corrupt. Run [notarize-prepare-to-redo](https://ci.eclipse.org/packaging/job/notarize-prepare-to-redo/) to rename the -signed file back to -tonotarize and then re-run the [notarize job](https://ci.eclipse.org/packaging/job/notarize-downloads/)
 - Other notes about notarization
   - **NOTE** It seems perfectly normal that the notarize job needs to be run multiple times as so many notarization attempts fail due to 500 and 000 response codes from the notarization server. See [Bug 571669](https://bugs.eclipse.org/bugs/show_bug.cgi?id=571669)
   - **NOTE** Sometimes the notarization server has an error that causes a failure that requires Webmaster support. Error looks like "an existing transporter instance is currently uploading this package". To resolve request assistance in [Bug 573875](https://bugs.eclipse.org/bugs/show_bug.cgi?id=573875) (like what was done in Comment 11 of that bug). (TODO it may be possible to workaround this error by always using a different random ID when doing the notarization.)

packages/org.eclipse.epp.package.committers.feature/epp.website.xml

@@ -34,6 +34,6 @@ Click <a href="https://github.com/eclipse-egit/egit/issues">here</a> to open a b
   </MoreInfo>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-committers-2024-03-I" />
+  <product name="eclipse-committers-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.cpp.feature/epp.website.xml

@@ -22,6 +22,6 @@
   </packageMetaData>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-cpp-2024-03-I" />
+  <product name="eclipse-cpp-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.dsl.feature/epp.website.xml

@@ -27,6 +27,6 @@
   </MoreInfo>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-dsl-2024-03-I" />
+  <product name="eclipse-dsl-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.embedcpp.feature/epp.website.xml

@@ -29,6 +29,6 @@ To avoid compatibility issues with pre 6.x plug-ins, it is recommended to <b>cre
   </packageMetaData>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-embedcpp-2024-03-I" />
+  <product name="eclipse-embedcpp-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.java.feature/epp.website.xml

@@ -28,6 +28,6 @@
 
 
 	<!-- name, the name of the product, used in naming the created files. -->
-	<product name="eclipse-java-2024-03-I" />
+	<product name="eclipse-java-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.jee.feature/epp.website.xml

@@ -34,6 +34,6 @@ Click <a href="https://github.com/eclipse/wildwebdeveloper/issues">here</a> to r
   </MoreInfo>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-jee-2024-03-I" />
+  <product name="eclipse-jee-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.modeling.feature/epp.website.xml

@@ -24,6 +24,6 @@
   </packageMetaData>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-modeling-2024-03-I" />
+  <product name="eclipse-modeling-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.php.feature/epp.website.xml

@@ -35,6 +35,6 @@ Click <a href="https://github.com/eclipse/wildwebdeveloper/issues">here</a> to r
   </MoreInfo>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-php-2024-03-I" />
+  <product name="eclipse-php-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.rcp.feature/epp.website.xml

@@ -27,6 +27,6 @@
   </MoreInfo>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-rcp-2024-03-I" />
+  <product name="eclipse-rcp-2024-03-M3" />
 
 </configuration>

packages/org.eclipse.epp.package.scout.feature/epp.website.xml

@@ -31,6 +31,6 @@
   </MoreInfo>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-scout-2024-03-I" />
+  <product name="eclipse-scout-2024-03-M3" />
 
 </configuration>

releng/org.eclipse.epp.config/parent/pom.xml

@@ -37,13 +37,13 @@
     <!-- Name of the release (no milestone) -->
     <RELEASE_NAME>2024-03</RELEASE_NAME>
     <!-- Name of the milestone -->
-    <RELEASE_MILESTONE>I</RELEASE_MILESTONE>
+    <RELEASE_MILESTONE>M3</RELEASE_MILESTONE>
     <!-- Version of the release -->
     <RELEASE_VERSION>4.31.0</RELEASE_VERSION>
     <!-- Name release directory on download.eclipse.org -->
-    <RELEASE_DIR>202402011200</RELEASE_DIR>
+    <RELEASE_DIR>202402221200</RELEASE_DIR>
     <!-- SimRel Repo to build from -->
-    <SIMREL_REPO>https://download.eclipse.org/staging/2024-03/</SIMREL_REPO>
+    <SIMREL_REPO>https://download.eclipse.org/releases/2024-03/202402231000/</SIMREL_REPO>
     <!-- ID used to generate the filename of the packages -->
     <eclipse.simultaneous.release.id>${RELEASE_NAME}-${RELEASE_MILESTONE}</eclipse.simultaneous.release.id>
     <!-- Timestamp used in various places, e.g. the about dialog (see about.mappings) -->

releng/org.eclipse.epp.config/tools/upload-to-staging.sh

@@ -95,8 +95,8 @@ Last +1 received for each package and platform (apologies if I missed one of you
 
 Packages:
 committers - 2023-06 RC2
-cpp - 2024-03 M1
-dsl - 2024-03 M1
+cpp - 2024-03 M2
+dsl - 2024-03 M2
 embedcpp - 2023-12 RC2a
 java - 2023-12 RC1
 jee - 2023-09 RC2
@@ -106,11 +106,11 @@ rcp - 2023-12 RC2a
 scout - 2023-12 RC2a
 
 Platforms:
-Linux x86_64 - 2024-03 M1
+Linux x86_64 - 2024-03 M2
 Linux aarch64 - 2023-09 RC2
 Windows - 2023-12 RC1
 macOS x86_64 - 2023-12 RC2a
-macOS aarch64 - 2024-03 M1
+macOS aarch64 - 2024-03 M2
 
 Thank you for testing!