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.
If there is a regression how are we going to compare the behaviour with the promoted build?
Thanks & Regards,
Sarika
----- Original message ----- From: Ed Willink <ed.willink@xxxxxxxxx> Sent by: eclipse-dev-bounces@xxxxxxxxxxx To: eclipse-dev@xxxxxxxxxxx Cc: Subject: [EXTERNAL] Re: [eclipse-dev] [platform-releng-dev] Stop producing milestones p2 repository Date: Wed, Nov 25, 2020 9:37 PM
Hi
+1 - mostly I only consume I-builds
-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.