Preparation work for 4.37(2025-09) and open master for development

[MohananRahul]

This preparation work involves the following tasks. For previous issue please refer to #2849

• Create R4_36_maintenance branch
• Move 4.36-I builds to R4_36_maintenance branch #3073
• Create new test jobs for 4.37 #3075
• Configure SWT build scripts for 4.37 eclipse.platform.swt#2192
• Splash Screen for 4.37 (2025-09) #3077
• Create 4.37-I-builds repo
• POM and product version changes for 4.37 release #3088
  • Update product version number to 4.37 across build scripts
  • Move previous version to 4.36RC2 across build scripts
• Update version number in Mac's Eclipse.app for 4.37 #3089
• Clean forceQualifierUpdate files for doc bundles
• Update builds and repo cleanup scripts for 4.37 #3085
• Create new I-build job for 4.37 release
• Update check composites script to verify 4.37 repositories
• Update Comparator repo and eclipse run repo to 4.37-I-builds repo #3090
• Version bumps for 4.37 stream #3093
• Update previous release version to 4.36 GA across build scripts #3114
• Update build calendar for platform 4.37 release
• Update generic repos I-builds, Y-builds, P-builds to point to 4.37 repos

[HannesWell]

@MohananRahul when exactly do you plan to conduct this preparatory work?
I'm asking because I'm currently working on a Jenkins pipeline that automates and combines at least the following steps

• POM and product version changes for 4.37 release
• Update product version number to 4.37 across build scripts
• Move previous version to 4.36RC2 across build scripts
• Version bumps for 4.37 stream

maybe even for

• Update version number in Mac's Eclipse.app for 4.37

It should make the tedious version bumps in all submodules obsolete because it improves the timings, and ensures the new parent-pom is already deployed so that the automated version-bump workflow can already do the heavy lifting.

It would be nice to use that pipeline immediately, but at the same time I don't want to delay the re-opening of the master (a lot).

[MohananRahul]

@MohananRahul when exactly do you plan to conduct this preparatory work? I'm asking because I'm currently working on a Jenkins pipeline that automates and combines at least the following steps

Will soon after promoting RC2.

• POM and product version changes for 4.37 release
• Update product version number to 4.37 across build scripts
• Move previous version to 4.36RC2 across build scripts
• Version bumps for 4.37 stream

And will be triggered by creation of new Milestone?

maybe even for

• Update version number in Mac's Eclipse.app for 4.37

It should make the tedious version bumps in all submodules obsolete because it improves the timings, and ensures the new parent-pom is already deployed so that the automated version-bump workflow can already do the heavy lifting.

It would be nice to use that pipeline immediately, but at the same time I don't want to delay the re-opening of the master (a lot).

[HannesWell]

Will soon after promoting RC2.

Means today? Also the steps I highlighted? Because IIRC in the past that particular task was done in the week after. But if things happen faster even better. :) If that's the case, we can use it for the next release.

And will be triggered by creation of new Milestone?

My intention is to include the creation of milestones there as well. It will then centralize the tasks done much more.

[MohananRahul]

Yes, I usually begin the initial steps after RC2, but the key highlighted activities start from weekend/Monday.

[MohananRahul]

Will soon after promoting RC2.

Means today? Also the steps I highlighted? Because IIRC in the past that particular task was done in the week after. But if things happen faster even better. :) If that's the case, we can use it for the next release.

Yes, We can try it in this release.

[HannesWell]

Will soon after promoting RC2.

Means today? Also the steps I highlighted? Because IIRC in the past that particular task was done in the week after. But if things happen faster even better. :) If that's the case, we can use it for the next release.

Yes, We can try it in this release.

OK, great. I'll try hard to make it ready over the weekend and will let you know if I succeeded or not.

[HannesWell]

@MohananRahul I have created a first draft of the mentioned new Jenkins job at

• [Build] Add Jenkins pipeline to improve release preparation automation #3078

So far everything looks good and testing most parts of it in isolation worked well. I plan to run the final testing tomorrow so that it should by ready/submitted by tomorrow (European) evening.

[HannesWell]

@MohananRahul I have just completed #3078 and we now have a new Prepare Next Development Cycle Jenkins job perform the mentioned tasks (including milestone creation).

Would it fit to run it tomorrow (Tuesday) before noon (probably your today's morning) to have the handled tasks done and also as a final test/premier? Do you want to run it or should I run it? If you want to run it, be sure that you uncheck the DRY_RUN box, which is enabled by default as a safeguard:

I have also tested locally if the new job would already ensure that the automated version increment GH workflow can do it's job, but it seems that the currently empty 4.37-I-build repo makes it fail. I'll try to find a solution for that, but we'll probably only enjoy it for the next release in three months.

[MohananRahul]

@MohananRahul I have just completed #3078 and we now have a new Prepare Next Development Cycle Jenkins job perform the mentioned tasks (including milestone creation).
Would it fit to run it tomorrow (Tuesday) before noon (probably your today's morning) to have the handled tasks done and also as a final test/premier? Do you want to run it or should I run it? If you want to run it, be sure that you uncheck the DRY_RUN box, which is enabled by default as a safeguard:

Yea sure you can, Lets run now.

[MohananRahul]

Ran the prepare Job, failed to create milestone. prepare PR generated.

[HannesWell]

Ran the prepare Job, failed to create milestone. prepare PR generated.

Thanks for running it. I have to admit I underestimated the timeshift between you and me. It was very late for me when I wrote it (for me yesterday). But it worked relatively well, so my intervention wasn't necessary immediately. Although it didn't succeeded completely, I'm happy with the result.

In fact it failed already when creating PRs but very late, i.e. when attempting to create a PR for equinox.binaries, which failed because there are are no changes in that repo.
The only repo that was missed is p2.
I'm currently looking for a hot-fix so that we can get the required changes for the latter and have the milestones created.

[HannesWell]

I'm currently looking for a hot-fix so that we can get the required changes for the latter and have the milestones created.

The missing p2 PR has been created and milestones are on their way. After multiple failed attempts to handle all the special cases for the different repos in which milestones are created, I have now started a run that doesn't abort when an error occures in order to create the pending milestones. I'll investigate it afterwards.
But at least these tasks should be completed now.