I can only recommend we do the least disruptive thing possible. Firstly
because in these corona times, it seems involvement is lower than
normal. And secondly because when ship a next release we want people to
be able to update to it, so the question of whether EPP's sites will be
found by existing 2020-12 installations is relevant. These
installations point at https://download.eclipse.org/releases/latest
which should therefore continue to compose the EPP updates.
So again, I can only recommend caution and consideration before we
redesign the whole system on whims and assumptions.
On 04.02.2021 14:04, Mickael Istria wrote:
> I thought Jonah was solving this problem and already has a "fix" for it?
I think he's solving 1 instance of this problem, but not the whole
class. And the fix has some drawbacks (eg more p2 repositories
necessary to install certain packages).
On Thu, Feb 4, 2021 at 1:58 PM Ed Merks <[email protected]
<mailto:[email protected]>> wrote:
The whole community currently uses things like
https://download.eclipse.org/releases/latest/
<https://download.eclipse.org/releases/latest/> for one stop
shopping for updates. Surely changing that is not a good
solution to an internal/interim releng issue.
The repo would still be present in EPP, it's just that this wouldn't
contain the EPP artifacts anymore which would be in a separate
repository (eg
https://download.eclipse.org/technology/epp/packages/latest/
<https://download.eclipse.org/technology/epp/packages/latest/> )
enabled in EPP by default. So Check for Updates from EPP packages
would still work and EPP could more easily include non-SimRel-repo
artifacts like JustJ.
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
