Open jonahgraham opened 3 weeks ago
@merks I have done all the steps up until "Wait for announcement that the staging repo is ready" - Let me know if you need anything for #162 (Windows on ARM issue)
There are new JREs that include Windows Aarch64
https://download.eclipse.org/justj/jres/21/updates/release/21.0.5
FYI, I opened the following issue to update the web pages to support/display the new architectures on the download pages:
https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org/-/issues/654
The EPP Release Process
This guide contains the step-by-step process to complete an EPP release.
The individual releases are tracked with endgame issues on GitHub issues. 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.
Steps for all Milestones and RCs:
epp.website.xml
-incubation
and(includes Incubating components)
are not used in packageMetaData anymore (See Bug 564214)url=
(notice the blank before url) inepp.website.xml
to see which ones are contained in the different packages.epp.product
files.*.product/p2.inf
files.icons
root directory.[releng] Prepare repo for 2020-12 M1
. In particular, check:2021-03-R
->2021-06-M1
, on RC2 set it toR
the qualifier e.g.2021-03-RC1
->2021-03-R
). Except foreclipse.simultaneous.release.name
which should go from2021-03 (4.19.0)
->2021-06 M1 (4.20.0 M1)
on M1 and2021-03 RC1 (4.19.0 RC1)
->2021-03 (4.19.0)
on RC2packages/*/epp.website.xml
forproduct name=
lineRELEASE_NAME
,RELEASE_MILESTONE
,RELEASE_DIR
,SIMREL_REPO
Variables in parent pomreleng/org.eclipse.epp.config/parent/pom.xml
SIMREL_REPO
should be updated to the URL published in the email to cross-project-issues announcing SimRel repo is ready for EPP buildeclipse.simultaneous.release.name
eclipse.simultaneous.release.name
remove qualifier i.e. it should be2020-12 (4.18.0)
eclipse.simultaneous.release.name
remove qualifier i.e. it should be2020-12 M1 (4.18.0 M1)
releng/org.eclipse.epp.config/tools/promote-a-build.sh
needs updatingSIMREL_REPO
inreleng/org.eclipse.epp.config/parent/pom.xml
if not done above.releng/org.eclipse.epp.config/tools/setGitDate
(link) script. This script will make a local commit you need to push.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 to rename the -signed file back to -tonotarize and then re-run the notarize job2020-03-M2
2020-03
2020-03-M2
org.eclipse.epp.package.*
features and bundles have the timestamp of the forced qualifier update or laterhttps://download.eclipse.org/staging/2024-12/
- NOTE UseSIMREL_REPO
if the staging repo has been updated since theSIMREL_REPO
location was created.https://download.eclipse.org/technology/epp/staging/repository/
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.2020-03 M3
)DRY_RUN
mode to ensure that the output is correct before it is copied to download.eclipse.org.DRY_RUN
can be done earlier in the day and is a good way to increase the chance that the final promotion step will be successful.SIMREL_REPO
to the staging repo so CI builds run against CI of SimRel (e.g. see this gerrit)R
build the release is initially published to a temporary location and then moved to theR
directory later. Make a note in the email where the temporary location is.On all milestone/release days
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.
24-48 Hours Before Final release day
git tag --annotate 2020-03_R -m"2020-03 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b
R
.Renaming the directory can be done with a script like TODO: make a job for this :
On Final release day
These jobs should be completed by approximately 10am Ottawa time on release days.