From a7d52fff82018b5d536be4412aa1caa091426b3b Mon Sep 17 00:00:00 2001 From: Ed Merks Date: Sun, 4 Jan 2026 14:38:46 +0100 Subject: [PATCH] Modernize and improve the README.md and the CONTRIBUTING.md - Fix typos in RELEASE.md. --- CONTRIBUTING.md | 96 +++++++++++++++------------------------ README.md | 116 ++++++++++++++++++++++++------------------------ RELEASING.md | 52 +++++++++++----------- 3 files changed, 120 insertions(+), 144 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 76def73c..602d0381 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,78 +1,52 @@ -Contributing to the Eclipse Packaging Project (EPP) -=================================================== +# Contributing to the Eclipse Packaging Project (EPP) -Thanks for your interest in this project. Contributions to the [Eclipse Packaging Project (EPP)] [1] are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. +Thanks for your interest in this project. +Contributions to the [Eclipse Packaging Project](https://projects.eclipse.org/projects/technology.packaging) are most welcome. +There are many ways to contribute, from entering high-quality issue reports, to contributing code or documentation changes. -Project description: --------------------- - -The objectives of the Eclipse Packaging project are to - -- create *entry level downloads* based on defined user profiles for the [Eclipse Simultaneous Release] [2]. The project defined and created the EPP downloads of Java Developer, Enterprise Java Developer, C/C++ Developer, RCP Developer, and more. These downloads are available from the main [Eclipse download page] [3]. -- provide a platform that allows the creation of packages (zip/tar/dmg downloads) from an p2 repository. The core technology of the project enables the creation of download packages that are created by bundling Eclipse features from one or multiple Eclipse p2 repositories. - -For more information, please go to the [Eclipse Packaging Project overview page] [4] or to the [EPP web site] [1]. - - -Developer resources: --------------------- - -Information regarding source code management, builds, coding standards, and more. - -- - -- Nightly builds are created on the project's Jenkins instance at . -- For instructions on how to run a build locally, follow the instructions of the README included in the root of this Git repository. - -Create an Eclipse Development Environment ------------------------------------------ +## Create an Eclipse Development Environment [![Create Eclipse Development Environment for EPP](https://download.eclipse.org/oomph/www/setups/svg/EPP.svg)](https://www.eclipse.org/setups/installer/?url=https://raw.githubusercontent.com/eclipse-packaging/packages/master/releng/org.eclipse.epp.config/oomph/EPPConfiguration.setup&show=true "Click to open Eclipse-Installer Auto Launch or drag onto your running installer's title area") -Contributor License Agreement: ------------------------------- - -Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA). - -- - -Contact: --------- - -Contact the project developers via the project's "dev" mailing list. - -- - -Search for bugs: ----------------- - -This project uses Bugzilla to track ongoing development and issues. - -- +## Developer Resources -Create a new bug: ------------------ +For instructions on how to run a build locally, follow the instructions of the [README.md](README.md#build-locally). -Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome! +# Eclipse Contributor Agreement -- +Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Contributor Agreement: +- [https://www.eclipse.org/legal/eca/](https://www.eclipse.org/legal/eca/) -EPP Committer and Maintainer Policy ------------------------------------ +## Contact -In EPP, the "maintainer" of a package is a committer in EPP. Partially so they can do work on their package, and also so that can participate in project discussions and decisions that effect the project or whole set of EPP packages. +Please ask questions via [discussions](https://github.com/eclipse-packaging/packages/discussions). -Historical note 1: in 2010, the current set of committers were "seeded" by making all current maintainers committers. Prior to that, there was only one active committer, the Project Lead, Markus Knauer, which was less than ideal for many reasons. Now that time has passed, it was thought best to document the EPP project's policy on making new people committers and maintainers of packages (either new packages, or transfer "ownership" of an existing package). In particular, it was decided to follow "the Orbit model" of committership and package "owner". +## Issues -Historical note 2: this policy used to live on the wiki and was moved to the git repo from: https://wiki.eclipse.org/EPP/EPP_Committer_and_Maintainer_Policy +This project uses [GitHub issues](https://github.com/eclipse-packaging/packages/discussions) to track ongoing development and issues. +Be sure to search for existing bugs before you create another one. +Contributions are always welcome! -If someone is a committer on another Eclipse project, and they state they are interested in contributing and maintaining an EPP package (or, transferring ownership of an existing EPP package), that history with other Eclipse projects suffices for them to be nominated and voted-in as a committer. This differs from most other projects where, for good reason, a person must (usually) have a history of contributions to that specific project, not just Eclipse in general. There still could be reasons an existing committer would note "no" (-1) for a nomination, for example, "no, I am the current maintainer and I do not agree to this!" ... or some other fairly large issue. Normally people do not vote "0" just because they have no first hand knowledge of a person's committer history (as they might on other projects), but vote "+1" if basic criteria are met, to be welcoming and supportive of new people coming in. +## EPP Committer and Maintainer Policy -Normally, as with most other Eclipse projects, unless a committer explicitly "resigns" there would be no automatic removal of a committer just because package responsibility is transferred, except eventually the usual "inactive" reasons would apply ... if someone is no longer responsible for maintaining a package and has not been active on mailing lists, etc., for a period of 6 months or so, the Project Lead can remove them via Eclipse Portal for "inactivity". And, of course, committers should explicitly resign, when appropriate, such as they are changing responsibilities and know they have no interest or time to be involved. +For each EPP package, +there is a commiter who is the package _maintainer_. +The maintainer is expected to participate in overall project discussions and to be involved in making decisions that affect the maintained package. +If someone is a committer on another Eclipse project, +and they state they are interested in contributing and maintaining an EPP package +or, transferring ownership of an existing EPP package, +that history with other Eclipse projects suffices for them to be nominated and voted-in as a committer. +This differs from most other projects where, for good reason, a person must (usually) have a history of contributions to that specific project, not just Eclipse in general. +There still could be reasons an existing committer would note "no" (-1) for a nomination, +for example, "no, I am the current maintainer and I do not agree to this!" +Normally people do not vote "0" just because they have no first hand knowledge of a person's committer history (as they might on other projects), +but vote "+1" if basic criteria are met, to be welcoming and supportive of new people coming in. -[1]: http://eclipse.org/epp/ -[2]: https://github.com/eclipse-simrel/.github/blob/main/wiki/Simultaneous_Release.md -[3]: https://www.eclipse.org/downloads/eclipse-packages/ -[4]: https://projects.eclipse.org/projects/technology.packaging +Normally, as with most other Eclipse projects, +unless a committer explicitly "resigns" there would be no automatic removal of a committer just because package responsibility is transferred, +except eventually the usual "inactive" reasons would apply. +If someone is no longer responsible for maintaining a package and has not been active on mailing lists, issues, or discussions for a period of roughly six months, +the Project Lead can remove them via Eclipse Portal for "inactivity". +And, of course, committers should explicitly resign, when appropriate, such as when they are changing responsibilities and know they have no interest or time to be involved. diff --git a/README.md b/README.md index affc7238..52e6ab54 100644 --- a/README.md +++ b/README.md @@ -1,90 +1,90 @@ # The EPP Build -The [Eclipse Packaging Project (EPP)](https://projects.eclipse.org/projects/technology.packaging/) provides the download packages based on the content of the yearly Simultaneous Release. -The download packages are provided from [www.eclipse.org/downloads/eclipse-packages/](https://www.eclipse.org/downloads/eclipse-packages/). +The [Eclipse Packaging Project (EPP)](https://projects.eclipse.org/projects/technology.packaging/) provides the download packages based on the content of the quaterly Simultaneous Release. +The download packages are avaiable at [https://www.eclipse.org/downloads/eclipse-packages/](https://www.eclipse.org/downloads/eclipse-packages/). -## Creating and releasing packages +## Creating and Releasing Packages -Please see [RELEASING.md](RELEASING.md) in this repo for instructions on the release process for the EPP project. +Please see [RELEASING.md](RELEASING.md) for instructions on the release process for the EPP project. + +## Contributing + +Please see [CONTRIBUTING.md](CONTRIBUTING.md) for instructions on how to setup an environment for contributing to the EPP project. ## Build Locally -It's _easy_ to run the build locally! All you need is Maven: +It's _easy_ to run the build locally! +All you need is Maven: mvn clean verify -will build all the packages (using automatically activated profiles) and the resulting zip/tar/dmg will be in `packages/org.eclipse.epp.package.${PACKAGE}.product/target/products`. -In addition the combined p2 site will be in `archive/repository`. +This will build all the packages (using automatically activated profiles) and the resulting `zip`, `tar.gz`, and `dmg` will be in `packages/org.eclipse.epp.package.${PACKAGE}.product/target/products`. +In addition, the combined p2 site will be in `archive/repository`. -### Build a single package +### Build a Single Package -If you want to build just a single package add the profile for the package you want to build, along with the profile to materialize the product: +If you want to build just a single package, add the profile for the package you want to build, along with the profile to materialize the product: mvn verify -Pepp.p2.common -Pepp.product.cpp -Pepp.p2.cpp -Pepp.materialize-products This build creates output in two places: -1. tar.gz/zip/dmg archives with the packages in `archive/` and -2. a p2 repository with the EPP artifacts in `archive/repository/`. - -### Build a single platform +1. The `zip`, `tar.gz`, and `dmg` archives for the packages in `archive/`. +2. The p2 repository with the EPP artifacts in `archive/repository/`. -By default the maven build runs the build for all platforms, this can be time consuming and can be changed to only build a limited number of platforms, a useful thing to do for testing changes locally. -There is no profile (PRs welcome!) to disabled other platforms, instead modify `releng/org.eclipse.epp.config/parent/pom.xml` to exclude the unwanted platforms in `target-platform-configuration`'s configuration. +### Build a Single Platform -### Windows users - -In the past the last step in the build process used to fail. -For further details see [bug 426416](https://bugs.eclipse.org/bugs/show_bug.cgi?id=426416). -If that happens again you can omit the `verify` stage and simply `package`. - - mvn clean package -Pepp.package.rcp -Pepp.materialize-products +By default the maven build runs the build for all platforms. +This can be time consuming and can be changed to only build a limited number of platforms +which is a useful for testing changes locally. +There is no profile (PRs welcome!) to disable other platforms. +Instead modify `releng/org.eclipse.epp.config/parent/pom.xml` to exclude the unwanted platforms in `target-platform-configuration`'s configuration. ### Available Profiles -Each package uses its own profile, with the zip/tar/dmg in `packages/org.eclipse.epp.package.${PACKAGE}.product/target/products`. -With the `epp.materialize-products` profile the zip/tar/dmg will be created, otherwise only the p2 site will be created. - -- epp.package.committers -- epp.package.cpp -- epp.package.embedcpp -- epp.package.dsl -- epp.package.java -- epp.package.jee -- epp.package.modeling -- epp.package.php -- epp.package.rcp -- epp.package.scout - -macOS dmg files can only be created within the Eclipse Foundation network. To enable creating -dmg files enable the `eclipse-package-dmg` profile. Without `eclipse-package-dmg` enabled, the .tar.gz -for macOS will be created regardless. - -With the signing profiles enabled, the build artifacts (bundles, features) and the -Windows and macOS executables are signed. This is done by using the Eclipse Foundation -internal signing service and can be activated only if the build is running there. - -- `eclipse-sign-jar` profile enables signing of the EPP bundles and jar files -- `eclipse-sign-mac` profile enables usage of macOS signing service -- `eclipse-sign-dmg` profile enables signing of the DMG files for the macOS platform (the `eclipse-package-dmg` needs to be enabled too!) -- `eclipse-sign-windows` profile enables usage of Windows signing service +Each package uses its own profile, with the resulting `zip`, `tar.gz`, and `dmg` in `packages/org.eclipse.epp.package.${PACKAGE}.product/target/products`. +With the `epp.materialize-products` profile the `zip`, `tar.gz`, and `dmg` will be created, otherwise only the p2 site will be created. + +- `epp.package.committers` +- `epp.package.cpp` +- `epp.package.embedcpp` +- `epp.package.dsl` +- `epp.package.java` +- `epp.package.jee` +- `epp.package.modeling` +- `epp.package.php` +- `epp.package.rcp` +- `epp.package.scout` + +The macOS `dmg` files can only be created within the Eclipse Foundation infrastructure. +To enable creating `dmg` files enable the `eclipse-package-dmg` profile. +Without `eclipse-package-dmg` enabled, only the `tar.gz` for macOS; +it will always be created regardless of the profile. + +With the signing profiles enabled, the build artifacts, i.e., bundles and features, +and the Windows and macOS executables are signed. +This is done by using the Eclipse Foundation internal signing service and can be activated only if the build is running there. + +- The `eclipse-sign-jar` profile enables signing of the EPP bundles and jar files. +- The `eclipse-sign-mac` profile enables usage of macOS signing service. +- The `eclipse-sign-dmg` profile enables signing of the DMG files for the macOS platform; `eclipse-package-dmg` profile needs to be enabled too. +- The `eclipse-sign-windows` profile enables usage of Windows signing service. ### Additional Configuration Possibilities -By default, the EPP build uses the content of the Eclipse Simultaneous Release _Staging_ -repository at 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: +By default, the EPP build uses the content of the Eclipse Simultaneous Release _Staging_ repository at 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: -Declipse.simultaneous.release.repository="https://download.eclipse.org/releases/2026-03" ### EPP Configuration File format -The individual EPP packages have a special file called epp.website.xml that defines various -pieces of information about the package. The format of the file is: +The individual EPP packages have a special file called `epp.website.xml` that specifies various details about the package. +The format of the file is as follows: ``` @@ -117,4 +117,4 @@ pieces of information about the package. The format of the file is: ... -``` +``` \ No newline at end of file diff --git a/RELEASING.md b/RELEASING.md index 1b359e79..6807434e 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -4,13 +4,14 @@ This guide contains the step-by-step process to complete an EPP release. The guide assumes that you have an IDE provisioned using the [Oomph setup](CONTRIBUTING.md#create-an-eclipse-development-environment). **Before** copying this file to create a new issue titled `EPP 2026-03 M1` with label `endgame`, update the names and versions, including those in this document. -- [ ] To update names and version, edit [org.eclipse.epp.releng.updater.Updater]( +- [ ] 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 value of `MILESTONE`, `PLATFORM_VERSION`, and possibly `EXECUTION_ENVIRONMENT` to the current appropriate values. - - Use `Run` tool-bar button drop-down menu to launch the `Update Versions` launch configuration + ) to set the values of `MILESTONE`, `PLATFORM_VERSION`, and possibly `EXECUTION_ENVIRONMENT` to the current appropriate values. + - Use the `Run` toolbar button drop-down menu to launch the `Update Versions` launch configuration to apply all the necessary name and version changes. -The individual releases are tracked with [endgame](https://github.com/eclipse-packaging/packages/labels/endgame) issues on GitHub issues. +The individual releases are tracked with [endgame](https://github.com/eclipse-packaging/packages/labels/endgame) issues on GitHub. + 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/Simultaneous_Release.md). @@ -24,7 +25,7 @@ Scroll down for the per-milestone/RC steps. - [ ] Update splash screen (once per release cycle, hopefully done before M1). See detailed [instructions](https://github.com/eclipse-packaging/packages/blob/master/packages/org.eclipse.epp.package.common/splash/INSTRUCTIONS.md). - [ ] Archive old releases (two R releases should stay on download.eclipse.org) to archive.eclipse.org and remove non-R downloads. - - This can be done through the web ui at https://download.eclipse.org/technology/epp/ + - This can be done through the web UI at https://download.eclipse.org/technology/epp/ **Steps for all Milestones and RCs:** @@ -46,8 +47,8 @@ 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. - Instead lookup the feature version [to be released with the release train](https://projects.eclipse.org/releases/). -- [ ] Synchronize the following - Remember to check branch, these links are to master, but around RC2 master may be setup for next release already. + Instead look up the feature version [to be released with the release train](https://projects.eclipse.org/releases/). +- [ ] 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/eclipse.platform.releng.tychoeclipsebuilder/eclipse.platform.repository/platform.product ) into all the `epp.product` files. @@ -59,26 +60,27 @@ Scroll down for the per-milestone/RC steps. ) into `icons` root directory. - [ ] Update the [Last Recorded +1 in the email template]( https://github.com/eclipse-packaging/packages/blob/master/releng/org.eclipse.epp.config/tools/upload-to-staging.sh - ) which any package and platform +1s that have been received since the last update. + ) which lists any package and platform +1s that have been received since the last update. - [ ] Wait for announcement that the staging repo is ready on [simrel-dev](https://accounts.eclipse.org/mailing-list/simrel-dev). An [example announcement](https://www.eclipse.org/lists/simrel-dev/msg00032.html). - [ ] Update `SIMREL_REPO` in `releng/org.eclipse.epp.config/parent/pom.xml` if not done above. - [ ] Update the build qualifiers to ensure that packages are all updated. See this [gerrit](https://git.eclipse.org/r/#/c/161075/) for an example. Commit all other changes before this step because this step will automatically create a Git commit specifically for the forced qualifier changes. - Use the `External Tools` tool-bar drop-down menu to launch the `Update Qualifiers` launch configuration. + Use the `External Tools` toolbar drop-down menu to launch the `Update Qualifiers` launch configuration. This runs the [setGitDate](releng/org.eclipse.epp.config/tools/setGitDate) bash script. - This script will make a local commit you need to push, **do not amend it** because the timestamp is relevant. + This script will make a local commit you need to push; **do not amend it** because the timestamp is relevant. - In some cases a respin/rebuild is needed and setGitDate needs to be run again. In that case you may need to manually add a minute or two to the applied timestamp in the script. - [ ] Run a [CI build](https://ci.eclipse.org/packaging/job/epp/job/master/) that includes the above changes. + - If the build fails, there may be the opportunity to continue the build rather than restart it. - If the build fails there may be the opportunity to continue the build rather than restart it. This is relatively underused option but enabled by the multi-step Jenkins build in the Jenkinsfile. For example, running the build with the previously successful steps commented out can produce a build. - [ ] Disable the [CI build](https://ci.eclipse.org/packaging/job/epp/job/master/) so that the build results are not overwritten while doing the promotion. - You can disable the project once it has fully started running, you don't have to wait for the build to finish. + You can disable the project once it has fully started running; you don't have to wait for the build to finish. - [ ] Check that there are no warnings in the console output. Especially look for warnings about failure to sign. - - If warnings about signings occur that leave the dmg unsigned and the build does not fail, + - If warnings about signing 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/ @@ -87,28 +89,28 @@ Scroll down for the per-milestone/RC steps. _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. + 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/) job. - 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. + It seems perfectly normal that the notarize job needs to be run multiple times because 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. + 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 work around this error by always using a different random ID when doing the notarization. - [ ] Sanity check the build for the following: - [ ] Download a package from the build's [staging output](https://download.eclipse.org/technology/epp/staging/). - - [ ] Made sure filenames contain expected build name and milestone, e.g., `2026-03-M1`. + - [ ] Make sure filenames contain expected build name and milestone, e.g., `2026-03-M1`. - [ ] 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-M1`. - [ ] From the `Console` open the `Host OSGi console` and use `ss -s INSTALLED` to verify that there are no bundles failing to resolve. + [ ] 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. - To test the upgrade an equivalent to the simrel release composite site needs to done. + 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/` - @@ -117,7 +119,7 @@ Scroll down for the per-milestone/RC steps. - `https://download.eclipse.org/justj/epp/milestone/latest` - This is needed when there is a new version of JustJ that is not also published as a release. For example, Java 21 between 2024-06 M1 and release date of 2024-06. - - [ ] Verify no non-EPP content is in the p2 repo + - [ ] Verify that no non-EPP content is in the p2 repo (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/). - [ ] Mark build as Keep forever. @@ -127,7 +129,7 @@ Scroll down for the per-milestone/RC steps. ) CI job to prepare build artifacts and copy them to download.eclipse.org. - [ ] _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 is copied to download.eclipse.org. - - This used to be done done late in the day to try and reduce impact of adding dozens of GB on the download server and having all the mirrors start to pick it up right away. + - This used to be done late in the day to try and reduce impact of adding dozens of GB on the download server and having all the mirrors start to pick it up right away. See [epp-dev emails that led to this decision](https://www.eclipse.org/lists/epp-dev/msg06317.html). However in 2024 the impact seems to no longer be a concern. This note is preserved until we know for sure there is no issue. @@ -148,11 +150,11 @@ Scroll down for the per-milestone/RC steps. 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: +- [ ] Check that this worked: copy the composite\*M1.jar files over the composite\*.jar files in https://download.eclipse.org/technology/epp/packages/2026-03/ - 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 + which is automatically triggered by SimRel's [SimRel Make Visible Job](https://ci.eclipse.org/simrel/view/All/job/simrel.releng.makeVisible/). **24-48 Hours Before Final release day** @@ -180,9 +182,9 @@ These jobs should be completed by approximately 10am Ottawa time on release days - [ ] Run the [Finalize Release]( https://ci.eclipse.org/packaging/job/finalize-release/ - ) CI job to create the "next" release and updated the "latest" release as follows: + ) CI job to create the "next" release and update the "latest" release as follows: - 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 specific https://download.eclipse.org/technology/epp/packages/yyyy-MM/. + 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. - On M1 release day this changes to a composite p2 repository with M1 content.