404 - Sorry! We couldn't find it when trying to view participating projects for 2026-03

[andrew-tram]

https://projects.eclipse.org/releases/2026-03

I'd like to see the participating projects and their respective version, but it seems like it's not accessible anymore. The last viewable one was for 2025-09 (https://projects.eclipse.org/releases/2025-09)

[jonahgraham]

The link at the end of https://github.com/eclipse-simrel/.github/blob/main/wiki/SimRel/2026-03.md#non-wiki-pages-related-to-the-release needs updating as the https://projects.eclipse.org/releases/2026-03 style URLs are no longer generated.

The new URL is https://eclipse.dev/simrel/?file=wiki/SimRel/2026-03_participants.json

[andrew-tram]

Oh gotcha, thank you!

[andrew-tram]

Well, I guess for posterity, would identifying the version of those projects be better? Some just point to /latest. Which makes sense for the current release, but what about when there are future releases?

[jonahgraham]

I created a PR to fix the incorrect URLs - #86

[jonahgraham]

As for versions, are you referring to lines like "new_and_noteworthy_url": "https://github.com/eclipse-acceleo/acceleo/releases/latest" in the json?

eclipse-simrel/simrel.build@99d5735 shows that many of the URLs were reconciled from a version to latest. I'll loop in @merks here if he can comment further on the data management here.

[merks]

The problem is identifying the versions. Given that "PMI" release records are no longer required, there's not much available to identify a version permanently...

This report contains links to release records, but I won't rely on them being accurate these days:

https://eclipse.dev/simrel/?file=report/report.md

Even the Platform skipped doing release records for years. And of course this is not so well historically recorded.

Those links are derived from the following which does have a traceable history relative to the release train deliverable:

https://github.com/eclipse-simrel/simrel.build/commits/main/simrel.aggran

If projects provided an N&N, which I've asked and suggested, that would provide permanent information, but often they point to a single document that evolved over time.

In the end, it's a herd of cats and I have enough trouble herding towards a quality deliverable...

Each release repository does have a report. Lots of versions there!!

https://download.eclipse.org/releases/2026-03/202603111000/buildInfo/archive/download.eclipse.org/releases/2026-03/202603111000/

---

I do wonder what problem is solved by knowing/having a version? I.e., what specifically would or could you be able to do with such a version?

[ewillink]

https://github.com/eclipse-simrel/simrel.build/commits/main/simrel.aggran

Yes. I find SimRel or rather the relevant *.aggrcon the best indication, particularly for fast moving projects such as EGIT that may have significant evolution for bleeding edge users compared to what went into SimRel.

[merks]

Yes. I find SimRel or rather the relevant *.aggrcon the best indication, particularly for fast moving projects such as EGIT that may have significant evolution for bleeding edge users compared to what went into SimRel.

Yes, that's why I ask, what will you do with a version?

It made me noticed just now that while I created the 2025-12 tag, I did not successfully push it to remote!

https://github.com/eclipse-simrel/simrel.build/releases/tag/2025-12

So one can look at what EGit contributed for 2025-12:

https://github.com/eclipse-simrel/simrel.build/blob/2025-12/egit.aggrcon

Of course even this is not always perfect, because a project might contribute an "RC" repository and later produce an actual release repository. In any case, one can determine from where each project's contribution originated...

[andrew-tram]

Not a big deal with the versions for me. So our product targets even year March Eclipse releases, and I do like to keep track of what projects were used during that SimRel. And from a build and packaging standpoint, I do like using the version URL of an update-site rather than latest, so I can quickly see what I'm using and it doesnt change as we do CD builds.

But like you said, it's easy enough to check back and see what we used.

[merks]

Stupid question. 😁 Why not use the release train repository? Just curious... 🐵

[ewillink]

Help->About Eclipse SDK->InstallationDetails | Configuration will tell you exactly what you are using. Trim it and use it as your cached reference.

[andrew-tram]

Yeah, I know how to identify what I'm using. I suppose I'm just used to see the spelled out table.

I suppose one case is if we needed to pull a project into our release train, Id like see what version was used at the time of a given SimRel release and use that as a starting point rather than the latest available. It could avoid issues like Java compatibility. Like if we were using Eclipse 2024-03 / Java 17 and tried to use the latest WWD that requires 21.