Closed MohananRahul closed 3 months ago
Go from JDT.Debug
Go from JDT.Debug
I would like to merge https://github.com/eclipse-jdt/eclipse.jdt.debug/pull/474 and follow up https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/1600
Any objections ?
Go from Platform.debug
Go from JDT.Debug
I would like to merge eclipse-jdt/eclipse.jdt.debug#474 and follow up eclipse-jdt/eclipse.jdt.ui#1600
Any objections ?
@iloveeclipse, would this re-spin the build process?
would this re-spin the build process?
Yes
I've merged mentioned PR's and triggered new build https://ci.eclipse.org/releng/job/Builds/job/I-build-4.33/119/
Go from PDE.
Go from PKI.
Go from JDT UI.
Two random test failures are tracked in:
Go from releng
Go from JDT Core. The lone failure is a transient one and doesn't happen locally.
Go from SWT.
Promoted to Simrel
Declare 4.33 RC1 A "go" is needed from all the components below to declare this milestone.
Current Candidate
Eclipse downloads: https://download.eclipse.org/eclipse/downloads/drops4/I20240822-0100
Build logs and/or test results (eventually): https://download.eclipse.org/eclipse/downloads/drops4/I20240822-0100/testResults.php
Software site repository: https://download.eclipse.org/eclipse/updates/4.33-I-builds
Specific (simple) site repository: https://download.eclipse.org/eclipse/updates/4.33-I-builds/I20240822-0100
Equinox downloads: https://download.eclipse.org/equinox/drops/I20240822-0100
Deadlines:
Friday, 2024- August -23, around 1 AM (Eastern): deadline for sign-off (or, by then, comment in this issue when you expect to sign-off). Friday, 2024 -August - 23, around 3 AM (Eastern): promote approved build to S-4.33RC1-*, contribute to simultaneous release repo, and announce to mailing lists. Remember to investigate and document here any failing JUnit tests.