(I only saw you sent your email after the last email I sent)
Thank you Hannes. I think that is the plan now. From 2022-09, milestones https://download.eclipse.org/releases/2022-09 will only point at the current milestone / release candidate / release. Note that it will remain a p2 composite repo of SimRel and EPP's contents.
If those repos won't be composites of all milestone/release-canidate repos anymore, it would be handy if the top-level repo of a release would only point to the latest milestone/RC.
This way for example "https://download.eclipse.org/releases/2022-06/" could be used from the publication of the first milestone onwards and would always lead to the latest version and finally stays on the GA.
Gesendet: Dienstag, 31. Mai 2022 um 19:42 Uhr Von: "Aleksandar Kurtakov" <akurtako@xxxxxxxxxx> An: "Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx> Betreff: Re: [cross-project-issues-dev] Multiple version of org.eclipse.sdk.feature.group in the 2022-06 simrel
If both of you (Jonah and Ed) don't use the composite repo, it's probably time to reconsider it as you're the two making the whole thing work.
P.S. Platform composite repo is smth I wish being simplified too so let's see what will come out of it.
You can imagine that when using the ongoing development stream, needing to do a rollback to undo some bad update might be a significant concern; garbage collection will quickly deletes unused artifacts (except if you're using a shared bundle pool).
On 31.05.2022 19:22, Jonah Graham wrote:
HI Nitin,
That is a question I have asked multiple times - I personally find it problematic having multiple milestones in one composite because it doesn't reveal problems until the release and slows down p2 resolution.
The last time this came up [1] I added a FAQ to simrel doc [2] - please let me know if that answers the question.
Anyway, this is why I now avoid using the composite in most cases, particularly the update from the last version test that is part of the EPP release procedures[3].