During the Eclipse Planning Council call today[1] we decided to change SimRel and EPP to no longer have multiple milestones as children in the p2 repo. This makes the state of the milestones closer to what the release will look like.
This change will come into effect for 2022-09 M1/M2 (i.e. after we release M2 to https://download.eclipse.org/releases/2022-09 the composite will not contain the M1 release anymore).
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].