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" <akurt...@redhat.com>
An: "Cross project issues" <cross-project-issues-dev@eclipse.org>
Betreff: Re: [cross-project-issues-dev] Multiple version of org.eclipse.sdk.feature.group in the 2022-06 simrel
Von: "Aleksandar Kurtakov" <akurt...@redhat.com>
An: "Cross project issues" <cross-project-issues-dev@eclipse.org>
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.
On Tue, May 31, 2022 at 8:35 PM Ed Merks <ed.me...@gmail.com> wrote:
_______________________________________________Jonah,
Note that the generated catalogs also don't use the composite
<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:p2="http://www.eclipse.org/oomph/p2/1.0">
<p2:Repository
url="" href="https://download.eclipse.org/technology/epp/packages/2022-06/202205261200" target="_blank">"https://download.eclipse.org/technology/epp/packages/2022-06/202205261200"/>
<p2:Repository
url="" href="https://download.eclipse.org/releases/2022-06/202205271000" target="_blank">"https://download.eclipse.org/releases/2022-06/202205271000">
<annotation
source="http://www.eclipse.org/oomph/setup/ReleaseTrain"/>
</p2:Repository>
</xmi:XMI>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].[3] See "Upgrade from previous release works" in https://git.eclipse.org/r/plugins/gitiles/epp/org.eclipse.epp.packages/+/refs/heads/master/RELEASING.mdHTHJonahOn Tue, 31 May 2022 at 12:40, Nitin Dahyabhai <thatnit...@gmail.com> wrote:Is there a benefit to having a composite of more than one milestone, or one build for that matter?On Tue, May 31, 2022 at 11:10 AM Ed Merks <ed.me...@gmail.com> wrote:Lars,
That's to be expected for a composite that is composed of all the
milestones for 2022-06 so far...
The concern is about duplicates in a simple repository, e.g.,
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/releases/2022-06/https___download.eclipse.org_releases_2022-06_202205271000.html
On 31.05.2022 16:59, Lars Vogel wrote:
> Hi,
>
> 2022-06 contains multiple versions of the Eclipse platform SDK, see
> https://github.com/eclipse-platform/eclipse.platform.releng/issues/32
> for a screenshot.
>
> The Eclipse TLP only contributes one version so someone else might
> contribute older versions.
>
> AFAIK the simrel is very concerned about multiple versions of plug-ins
> therefore I post this info here.
>
> Best regards, Lars
>
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev--_______________________________________________Regards,Nitin DahyabhaiEclipse WTP PMC
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev_______________________________________________cross-project-issues-dev mailing listcross-project-issues-dev@eclipse.orgTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Aleksandar Kurtakov
Red Hat Eclipse Team_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
