Closed jonahgraham closed 9 months ago
Build is complete and smoke tested and email scheduled to send once mirrors have been seeded.
I reset the checkmarks in preparation for RC2a and I am now working on producing that build.
RC2a build is running - https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/3051/
Build of RC2a is complete and smoke tested and email scheduled to send once mirrors have been seeded.
@jonahgraham
I've done the final steps, regenerated catalogs to use the new repositories, 2024-03, tested that latest and 2024-03 load, and tested that 2023-12/latest loads with IUs from the correct final release.
So I think we are done here.
Thanks @merks - we are done for 2023-12. On to 2024-03, I will make the new tracking issue soon.
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.gitk -- **/epp.product **/p2.inf
and make sure every change to included features in epp.product has a matching change in p2.inf. You should only have to look as far back as the last M or RC build.[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.[WARNING] Mirror tool: Messages while mirroring artifact descriptors.
per packageA terminally deprecated method in java.lang.System has been called
is OK when it is about setSecurityManager from ANT. When the security manager goes away for real we'll have to resolve this issue.The digest algorithms (md5) used to verify
is OK to ignore because we pull from SimRel. Over time there should be less of these warnings as projects rebuild their old repos to have modern signing. These warnings are typically seen on bundles which are old, such asorg.eclipse.update.feature,org.eclipse.license,2.0.2.v20181016-2210
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 asorg.eclipse.epp.package.common.feature
orepp.package.cpp.executable.gtk.linux.aarch64
)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/2023-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/
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)git tag --annotate 2020-03_R -m"2020-03 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b