Prepare for 2026-06

- Update branding images, including splash screen.

Author: merks

Jenkinsfile

@@ -10,7 +10,7 @@ pipeline {
 
     // check every 5 minutes for changes to the staging repo's content.jar
     URLTrigger(cronTabSpec: 'H/5 * * * *', entries: [URLTriggerEntry(
-                    url: 'https://download.eclipse.org/staging/2026-03/content.jar',
+                    url: 'https://download.eclipse.org/staging/2026-06/content.jar',
                     contentTypes: [
                         MD5Sum()
                     ]

README.md

@@ -78,14 +78,14 @@ This is done by using the Eclipse Foundation internal signing service and can be
 
 ### Additional Configuration Possibilities
 
-By default, the EPP build uses the content of the Eclipse Simultaneous Release _Staging_ repository at <https://download.eclipse.org/staging/2026-03/> as input.
+By default, the EPP build uses the content of the Eclipse Simultaneous Release _Staging_ repository at <https://download.eclipse.org/staging/2026-06/> as input.
 Sometimes it is desired to build against another release, e.g., a different milestone,
 or against a local mirror of this repository.
 This can be achieved by setting the Java property `eclipse.simultaneous.release.repository` to another URL.
 As an example, by adding the following argument to the Maven command line,
-the EPP build will read its input from the composite Eclipse 2026-03 repository:
+the EPP build will read its input from the composite Eclipse 2026-06 repository:
 
-    -Declipse.simultaneous.release.repository="https://download.eclipse.org/releases/2026-03"
+    -Declipse.simultaneous.release.repository="https://download.eclipse.org/releases/2026-06"
 
 ### EPP Configuration File format
 

RELEASING.md

@@ -3,7 +3,7 @@
 This guide contains the step-by-step process to complete an EPP release and assumes that you have an IDE provisioned using the [Oomph setup](
 https://github.com/eclipse-packaging/packages/blob/master/CONTRIBUTING.md#create-an-eclipse-development-environment).
 
-**Before** copying this file to create a new issue titled `EPP 2026-03 RC2` with label `endgame`, update the names and versions, including those in this document.
+**Before** copying this file to create a new issue titled `EPP 2026-06 M1` with label `endgame`, update the names and versions, including those in this document.
 - [ ] To update names and versions, edit [org.eclipse.epp.releng.updater.Updater](
       releng/org.eclipse.epp.config/org.eclipse.epp.releng.updater/src/org/eclipse/epp/releng/updater/Updater.java
       ) to set the values of `MILESTONE`, `PLATFORM_VERSION`, and possibly `EXECUTION_ENVIRONMENT` to the current appropriate values.
@@ -19,7 +19,7 @@ The individual releases are tracked with [endgame](https://github.com/eclipse-pa
 For each release (M1, M2, M3, RC1, RC2) an endgame ticket is created with the appropriate contents from the rest of this document:
 
 EPP releases happen for each milestone and release candidate according to the [Eclipse Simultaneous Release Plan](
-https://github.com/eclipse-simrel/.github/blob/main/wiki/SimRel/2026-03.md)
+https://github.com/eclipse-simrel/.github/blob/main/wiki/SimRel/2026-06.md)
 
 **Steps at the beginning of each release cycle, i.e., before M1:**
 
@@ -52,7 +52,7 @@ Scroll down for the per-milestone/RC steps.
   - [ ] Search for ` url=` (notice the blank before url) in `epp.website.xml` to see which ones are contained in the different packages.
   - [ ] Remember that some of the features will release new versions together with the new Eclipse release.
         Therefore using the _currently_ released version number may be wrong.
-        Look at the news links in [2026-03 Participants](https://eclipse.dev/simrel/?file=wiki/SimRel/2026-03_participants.json).
+        Look at the news links in [2026-06 Participants](https://eclipse.dev/simrel/?file=wiki/SimRel/2026-06_participants.json).
 - [ ] Synchronize the following - Remember to check the branch; these links are to master, but around RC2 master may be set up for the next release already.
   - [ ] Synchronize any changes to [platform.product](
         https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/products/eclipse-platform/platform.product
@@ -112,17 +112,17 @@ Scroll down for the per-milestone/RC steps.
   - [ ] Use the `External Tools` toolbar button drop-down menu to launch the `Prepare Staging Sanity Check` launch configuration. 
         This will automatically download the packages specified in the launch configuration to subfolders in `/org.eclipse.epp.packages/sanity-check` to make the follow steps easier.
   - [ ] Download a package from the build's [staging output](https://download.eclipse.org/technology/epp/staging/).
-  - [ ] Make sure filenames contain expected build name and milestone, e.g., `2026-03-R`.
-  - [ ] Splash screen says the expected release name with no milestone, e.g., `2026-03`.
-  - [ ] `Help -> About` says the expected build name and milestone, e.g., `2026-03-R`.
+  - [ ] Make sure filenames contain expected build name and milestone, e.g., `2026-06-M1`.
+  - [ ] Splash screen says the expected release name with no milestone, e.g., `2026-06`.
+  - [ ] `Help -> About` says the expected build name and milestone, e.g., `2026-06-M1`.
   - [ ] From the `Console`, open the `Host OSGi console` and use `ss -s INSTALLED` to verify that there are no bundles failing to resolve.
   - [ ] The `org.eclipse.epp.package.*` features and bundles have the timestamp of the forced qualifier update or later.
   - [ ] Upgrade from previous release works.
         The `Prepare Staging Sanity Check` automatically configures the available updates sites for this test.
         To test the upgrade an equivalent to the simrel release composite site needs to be done.
         Add the following software sites to available software, check for updates and then make sure stuff works.
         In particular check error log and that core features, e.g., JDT, Platform, have been upgraded.
-    - `https://download.eclipse.org/staging/2026-03/` -
+    - `https://download.eclipse.org/staging/2026-06/` -
         _NOTE_ Use `SIMREL_REPO` if the staging repo has been updated since the `SIMREL_REPO` location was created.
     - `https://download.eclipse.org/technology/epp/staging/repository/`
     - `https://download.eclipse.org/justj/epp/milestone/latest` - 
@@ -132,7 +132,7 @@ Scroll down for the per-milestone/RC steps.
        (especially justj, update [remove-justj-from-p2.xml](https://github.com/eclipse-packaging/packages/blob/master/releng/org.eclipse.epp.config/tools/remove-justj-from-p2.xml) if needed).
 - [ ] Edit the [Jenkins build](https://ci.eclipse.org/packaging/job/epp/job/master/lastBuild/).
   - [ ] Mark build as Keep forever.
-  - [ ] Edit Jenkins Build Information and name it, e.g., `2026-03 R`.
+  - [ ] Edit Jenkins Build Information and name it, e.g., `2026-06 M1`.
 - [ ] Run the [Promote a Build](
       https://ci.eclipse.org/packaging/job/promote-a-build/
       ) CI job to prepare build artifacts and copy them to download.eclipse.org.
@@ -166,7 +166,7 @@ This applies to all releases, i.e. M1, M2, M3, RC1 and R.
 Everything except R is typically the Friday around 9:30am Ottawa time and the R is the following Wednesday sometime before 10am in coordination with the SimRel release engineer.
 
 - [ ] Check that this worked:
-      copy the composite\*R.jar files over the composite\*.jar files in https://download.eclipse.org/technology/epp/packages/2026-03/ -
+      copy the composite\*M1.jar files over the composite\*.jar files in https://download.eclipse.org/technology/epp/packages/2026-06/ -
       this is done automatically with the
       [EPP Make Visible job](https://ci.eclipse.org/packaging/job/epp-makeVisible/)
       which is automatically triggered by SimRel's
@@ -175,8 +175,8 @@ Everything except R is typically the Friday around 9:30am Ottawa time and the R
 **24-48 Hours Before Final release day**
 
 - [ ] **24 Hours before Final release** Make sure files are in final location to allow downloads to mirror.
-  - [ ] Tag the release, e.g., `2026-03_R`.
-        Example command line: `git tag --annotate 2026-03_R -m"2026-03 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b`.
+  - [ ] Tag the release, e.g., `2026-06_R`.
+        Example command line: `git tag --annotate 2026-06_R -m"2026-06 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b`.
   - [ ] Run the [Rename Provisional to Final](
         https://ci.eclipse.org/packaging/job/rename-provisional-to-final/
         ) CI job to rename the provisional release milestone to final directory.
@@ -201,7 +201,7 @@ These jobs should be completed by approximately 10am Ottawa time on release days
   - The current release needs to be promoted as "latest" under https://download.eclipse.org/technology/epp/packages/latest/.
     This should be a composite pointing to a specific https://download.eclipse.org/technology/epp/packages/yyyy-MM/.
   - The _next_ release sub-directory needs to be created immediately.
-    - When 2026-03 is released, a directory 2026-06 must be created with an empty p2 composite repository pointing to 2026-03 until M1.
+    - When 2026-06 is released, a directory 2026-09 must be created with an empty p2 composite repository pointing to 2026-06 until M1.
     - On M1 release day this changes to a composite p2 repository with M1 content.
   - [ ] _Optional - useful when testing changes to the promotion scripts:_
        - Run the build once in `DRY_RUN` mode to ensure that the output is correct before it applies changes to download.eclipse.org.

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

@@ -29,11 +29,11 @@ Click <a href="https://github.com/eclipse-egit/egit/issues">here</a> to open a b
   </packageMetaData>
   <MoreInfo>
   <NewAndNoteworthy
-    url="https://eclipse.dev/eclipse/news/4.39/"
+    url="https://eclipse.dev/eclipse/news/4.40/"
     project="Eclipse Platform" />
   </MoreInfo>
 
   <!-- name, the name of the product, used in naming the created files. -->
-  <product name="eclipse-committers-2026-03-R" />
+  <product name="eclipse-committers-2026-06-M1" />
 
 </configuration>

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

@@ -2,7 +2,7 @@
 <feature
       id="org.eclipse.epp.package.committers.feature"
       label="EPP Eclipse IDE for Eclipse Committers Feature"
-      version="4.39.0.qualifier"
+      version="4.40.0.qualifier"
       provider-name="Eclipse Packaging Project"
       plugin="org.eclipse.epp.package.committers"
       license-feature="org.eclipse.license"

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

@@ -21,7 +21,7 @@
   <parent>
     <groupId>org.eclipse.epp</groupId>
     <artifactId>org.eclipse.epp-feature-parent</artifactId>
-    <version>4.39.0-SNAPSHOT</version>
+    <version>4.40.0-SNAPSHOT</version>
     <relativePath>../../releng/org.eclipse.epp.config/parent/feature</relativePath>
   </parent>
 

packages/org.eclipse.epp.package.committers.product/epp.p2.inf

@@ -2,7 +2,7 @@ instructions.configure=\
   mkdir(path:${installFolder}/dropins);
 
 properties.1.name = org.eclipse.equinox.p2.description
-properties.1.value = 2026-03 Release of the Eclipse Committers package.
+properties.1.value = 2026-06 Release of the Eclipse Committers package.
 
 properties.2.name = org.eclipse.equinox.p2.provider
 properties.2.value = Eclipse Packaging Project

packages/org.eclipse.epp.package.committers.product/epp.product

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <?pde version="3.5"?>
 
-<product name="Eclipse IDE for Eclipse Committers" uid="epp.package.committers" id="org.eclipse.epp.package.committers.product" application="org.eclipse.ui.ide.workbench" version="4.39.0.qualifier" type="mixed" includeLaunchers="true" autoIncludeRequirements="true">
+<product name="Eclipse IDE for Eclipse Committers" uid="epp.package.committers" id="org.eclipse.epp.package.committers.product" application="org.eclipse.ui.ide.workbench" version="4.40.0.qualifier" type="mixed" includeLaunchers="true" autoIncludeRequirements="true">
 
 <!--
 
@@ -247,7 +247,7 @@ United States, other countries, or both.
 
    <features>
       <!-- common features that all products have -->
-      <feature id="org.eclipse.epp.package.common.feature" version="4.39.0.qualifier"/>
+      <feature id="org.eclipse.epp.package.common.feature" version="4.40.0.qualifier"/>
       <feature id="org.eclipse.platform" installMode="root"/>
       <feature id="org.eclipse.epp.mpc" installMode="root"/>
       <feature id="org.eclipse.oomph.setup" installMode="root"/>
@@ -269,7 +269,7 @@ United States, other countries, or both.
       <feature id="org.eclipse.mylyn.reviews.feature" installMode="root"/>
 
       <!-- product specific contents -->
-      <feature id="org.eclipse.epp.package.committers.feature" version="4.39.0.qualifier"/>
+      <feature id="org.eclipse.epp.package.committers.feature" version="4.40.0.qualifier"/>
       <feature id="org.eclipse.jdt" installMode="root"/>
       <feature id="org.eclipse.jdt.bcoview.feature" installMode="root"/>
       <feature id="org.eclipse.pde" installMode="root"/>
@@ -307,8 +307,8 @@ United States, other countries, or both.
    </configurations>
 
    <repositories>
-      <repository location="https://download.eclipse.org/eclipse/updates/4.39" name="The Eclipse Project Updates" enabled="true" />
-      <repository location="https://download.eclipse.org/releases/2026-03" name="2026-03" enabled="true" />
+      <repository location="https://download.eclipse.org/eclipse/updates/4.40" name="The Eclipse Project Updates" enabled="true" />
+      <repository location="https://download.eclipse.org/releases/2026-06" name="2026-06" enabled="true" />
    </repositories>
 
 </product>

packages/org.eclipse.epp.package.committers.product/pom.xml

@@ -20,7 +20,7 @@
   <parent>
     <groupId>org.eclipse.epp</groupId>
     <artifactId>org.eclipse.epp-product-parent</artifactId>
-    <version>4.39.0-SNAPSHOT</version>
+    <version>4.40.0-SNAPSHOT</version>
     <relativePath>../../releng/org.eclipse.epp.config/parent/product</relativePath>
   </parent>
 

packages/org.eclipse.epp.package.committers/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %pluginName
 Bundle-SymbolicName: org.eclipse.epp.package.committers;singleton:=true
-Bundle-Version: 4.39.0.qualifier
+Bundle-Version: 4.40.0.qualifier
 Bundle-Vendor: %providerName
 Bundle-Localization: plugin
 Bundle-RequiredExecutionEnvironment: JavaSE-21