You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[RelEng] Update build configurations with release in release promotion
This automates the update of build configurations with the final GA
release versions on the master and corresponding maintenance branch, by
updating all versions or URLs that were pointing to a RC or specific
I-build to point to the final GA release.
On the maintenance branch also set a fixed version for ECJ.
Copy file name to clipboardExpand all lines: RELEASE.md
+2-18Lines changed: 2 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,6 +93,8 @@ The actual steps to release
93
93
*#### **Promote to GA**
94
94
- After Simrel declares RC2 (usually the Friday before release) run the [Promote Build](https://ci.eclipse.org/releng/job/Releng/job/promoteBuild/) job to promote RC2 (or RC2a).
95
95
-`DROP_ID`: Final delease candidate's ID, e.g.: `S-4.36RC2-202505281830/`
96
+
- This will create pull requests to update the build configuration on the master and corresponding maintenance branch to the promoted release.
97
+
- Only submit them AFTER the release was finally published.
96
98
- You can subscribe to [cross-project-issues](https://accounts.eclipse.org/mailing-list/cross-project-issues-dev) to get the notifications on Simrel releases.
97
99
***Contribute to SimRel**
98
100
- If SimRel is not updated before the I-builds are cleaned up (specifically the build for RC2/GA) it will break.
@@ -120,29 +122,11 @@ The release is scheduled for 10AM EST. Typically the jobs are scheduled beforeha
120
122
- For the Y and P build parameters it's important to know whether or not Y and P builds were run during the release. Since they correspond to java releases on a 6 month cycle, typically they are built in odd-numbered releases.
121
123
The existing builds are kept for one release, then cleaned up before the next stream that will have Y and P builds. it's convoluted and I dont want to type it out. Remove Y builds on even releases.
122
124
- If something doesn't get cleaned up properly you can use Use the [list artifacts](https://ci.eclipse.org/releng/view/Cleanup/job/list_artifacts_from_download_server/) job to generate ta list of what's on the download server and either create a new job to clean it up or update and rerun the cleanup job as appropriate.
123
-
***Set Previous Release to GA**
124
-
- Everything that was updated to RC2 (see below) should now use the released build.
125
125
126
126
### **Preparation for the next Release**
127
127
After RC2 create an issue to track preparation work for the next stream (see [Preparation work for 4.25 (2022-09)](https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/284)).
128
128
- A script to create this issue exists [here](scripts/newReleasePrep.sh) for those who have the hub cli tool installed. The process has been in flux recently so please update the script if necessary, but it provides a helpful template since most tasks in the previous release's issue become links.
129
129
130
-
#### **Maintenance Branches:**
131
-
***Update maintenance branch with release version**
132
-
- Once the I-build repo is removed for the previous release the maintenance branch will have to use the release location, i.e. any references to `https://download.eclipse.org/eclipse/updates/4.25-I-builds/` will need to be updated to `https://download.eclipse.org/eclipse/updates/4.26/R-4.26-202211231800/`
133
-
- Functionally this means:
134
-
- Update the ECLIPSE_RUN_REPO in the [cje-production](cje-production) buildproperties.txt files
135
-
- Update `eclipse-sdk-repo` in [eclipse-platform-parent/pom.xml](eclipse-platform-parent/pom.xml)
136
-
- This step can be prepared ahead of time but can't be merged until the release build has been promoted and the update site exists.
137
-
***Update ECJ compiler** in the platform build (if it needs to be updated).
138
-
* To find the new *unqualified* compiler version:
139
-
- Go to the update site for the release candidate
140
-
- Click `plugins`
141
-
- Find the *unqualified* version of the artifact `org.eclipse.jdt.core.complier.batch_${ecjversion}.jar`, i.e. the version consisting only of the _major_._minor_._service_ part, but without qualifier.
142
-
It's the version of the `org.eclipse.jdt:ecj` artifact at Maven-Central, about to be relased.
143
-
* Update the `cbi-ecj-version` in [eclipse.platform.releng.aggregator/eclipse-platform-parent/pom.xml](https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse-platform-parent/pom.xml)
144
-
to the exact version of the to be released`org.eclipse.jdt.core.complier.batch` bundle, e.g.: `3.40.0`
145
-
146
130
#### **Update the Build Calendar:**
147
131
- Create an [issue](https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/289) and update the [build calendar](https://calendar.google.com/calendar/u/0?cid=cHJmazI2ZmRtcHJ1MW1wdGxiMDZwMGpoNHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ) for the next GA release based on the [Simultaneous Release schedule](https://wiki.eclipse.org/Simultaneous_Release).
148
132
- Each stream has its own [wiki](https://wiki.eclipse.org/Category:SimRel-2022-06) page with a more detailed schedule.
0 commit comments