It is ok not to have them in a different repository but it should be available over the full release cycle. As currently only Monday's build is available on https://download.eclipse.org/eclipse/downloads/ and the milestones builds happen on Wednesday/Thursday we will not have access to M1 build during M3 or RC phase.
That's not true. Just look at https://download.eclipse.org/eclipse/updates/4.18-I-builds/ every single build is there. The fact it's not listed on the download page is just to not crowd it. And even right now there is no obvious way how to get M1 build from that page.
If there is a regression how are we going to compare the behaviour with the promoted build?
-1 - but when there is a problem it is important to have a stable stepping stone
The problem is that not enough I-builds are always kept to guarantee that the milestone contribution is available, or indeed tagged in any recognisable way.
-1 again N-builds have already gone, so what is the difference between first attempt experiment and last attempt production ready? There must be a level at which accidents happen but are not exposed to all project N-builds.
Regards
Ed Willink
On 25/11/2020 15:48, Szymon Ptaszkiewicz wrote:
+1 for using I-Builds only.
Some time ago I proposed to use non-versioned update site URL [1]. Since we are now releasing more often and the concern of regular URL updates for consumers is more visible, maybe it would be good to revisit the idea of non-versioned URL and use that more often?
śr., 25 lis 2020 o 13:15 Mickael Istria <mistria@xxxxxxxxxx> napisał(a):
+1. I personally never use milestones; being on latest I-Build provides a shorter feedback loop IMO, so if milestones do take some effort, while we have already something that provide a faster feedback loop and more agility for less effort; it's probably worth dropping the extra steps.