Re: [simrel-dev] Staging for SimRel 2025-09 M1 is Complete | ACTION REQU

[LORENZO Vincent <vincent.lorenzo@xxxxxx>]

Hello everybody,

                We inform you that Papyrus and XWT will not participate to the 2025-09 release.

 

https://github.com/eclipse-simrel/simrel.build/pull/950

 

Regards,

--

Vincent LORENZO

 

 

De : simrel-dev <simrel-dev-bounces@xxxxxxxxxxx> De la part de Ed Merks via simrel-dev
Envoyé : jeudi 10 juillet 2025 09:28
À : simrel-dev@xxxxxxxxxxx
Cc : Ed Merks <ed.merks@xxxxxxxxx>
Objet : [simrel-dev] Staging for SimRel 2025-09 M1 is Complete | ACTION REQUIRED: Do not include non-project content in features

 

The staging repository content of

  https://download.eclipse.org/staging/2025-09/

has been promoted to the following repository for 2025-09 M1:

  https://download.eclipse.org/releases/2025-09/202507111000/

This is ready for consumption by EPP.

It will become visible in the composite as scheduled Friday, July 11, 2025:

  https://download.eclipse.org/releases/2025-09

___________________

Reminder:  Do not include non-project content in features

https://eclipse.dev/eclipse/markdown/?file=eclipse-simrel/.github/main/wiki/SimRel/Simultaneous_Release_Requirements.md#do-not-include-non-project-content-in-features

In the coming weeks, I will be tracking down the offenders and if you are at the bottom of the dependencies graph I will disable your contribution:

https://raw.githubusercontent.com/merks/test/master/report.svg

___________________

We're regressing on the duplicates primarily because of including non-project content in features.

https://download.eclipse.org/staging/2025-09/buildInfo/archive/download.eclipse.org/staging/2025-09/

1. We need a DLTK update https://github.com/eclipse-dltk/dltk.core/issues/5 but that appears completely stalled.
2. My fault for contributing a late M1a of the Platform in Tuesday to avoid regression behavior in editors using the reconciler, though I do wonder why RAP to includes Platform projects in RAP features; see reminder above.
3. We need a WTP update and this is caused by including Jetty in WTP's features; see reminder above.