An online editable version of this document is on hackmd.io, updates should be copied to Eclipse's git repo. The Eclipse version is the official one.
This guide contains the step-by-step process to complete an EPP release.
EPP releases happen for each milestone and release candidate according to the Eclipse Simultaneous Release Plan.
Steps for M1:
4.14
-> 4.15
); this is a large change including pom.xml, feature.xml, MANIFEST.MF, epp.website.xml, and epp.productSteps for all Milestones and RCs:
-incubation
and (includes Incubating components)
are not used in packageMetaData anymore (See Bug 564214) url=
(notice the blank before url) in epp.website.xml
to see which ones are contained in the different packages.Update strings for 2020-09 M2
. In particular, check:packages/*/epp.website.xml
for product name=
linereleng/org.eclipse.epp.config/parent/pom.xml
releng/org.eclipse.epp.config/tools/setGitDate
script. This script will make a local commit you need to push.artifact/org.eclipse.epp.packages/archive/
2020-03-M2
2020-03
2020-03-M2
org.eclipse.epp.package.*
features and bundles have the timestamp of the forced qualifier update or later2020-03 M3
)maven.build.timestamp=20191212-1212 eclipse.simultaneous.release.build=20191212-1212 build=20191212-1212
DRY_RUN
mode to ensure that the output is correct before it is copied to download.eclipse.org.curl -O http://download.eclipse.org/technology/epp/packages/2020-09/compositeContent.jar
and curl -I http://download.eclipse.org/technology/epp/packages/2020-09/compositeContent.jar
must return 404.CHECKPOINT=RC1 REPO_ROOT=/home/data/httpd/download.eclipse.org/technology/epp/packages rsync --group --verbose ${REPO_ROOT}/compositeArtifacts${CHECKPOINT}.jar ${REPO_ROOT}/compositeArtifacts.jar rsync --group --verbose ${REPO_ROOT}/compositeContent${CHECKPOINT}.jar ${REPO_ROOT}/compositeContent.jar
git tag -s -a 2020-03_R -m"2020-03 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b