Prepare 4.37 development

[eclipse-releng-bot]

Prepare development of Eclipse 4.37.
This includes:

• Updating the version of the Maven parent, all references to it and the Eclipse products to 4.37
• Updating the release version to 4.37 across build scripts
• Updating the previous release version to the current Release-Candidate: S-4.36RC2-202505281830

[HannesWell]

@MohananRahul I just saw from the git history that you used Squash-and-Merge to submit this and therefore all the intentionally separated commits are now one. Furthermore that mehtod changes the commit metadata in a usually undesired manner. See also the discussion at

• Null pointer check added for system package eclipse-pde/eclipse.pde#1455 (comment)

As PDE PL I have therefore disabled Squash-and-merge so that only Rebase-and-Merge is available:

• Disable squash-and-merge submission eclipse-pde/.eclipsefdn#4

This way the PR authors can and have to decide on their own how changes are separated in commit (or if there is only one commit). But that has to be decided by the Platform PLs.

However I personally recommend to always use Rebase-and-Merge.

[MohananRahul]

However I personally recommend to always use Rebase-and-Merge.

Thanks. noted.

[akurtakov]

@HannesWell If you create PR that disables squash and merge for all platform repos I'll push it as PL.