On Thu, Aug 26, 2021 at 3:49 PM Frederic Gurr < frederic.g...@eclipse-foundation.org> wrote:
> Hi, > > Are there any good reasons to keep milestone repos, release candidate > repos and repos that were replaced with a respin around for an extended > time (or forever)? > > @Jonah: A similar question could be asked for the retention time of EPP > milestone and release candidates _repos_. > > This should not concern the EPP artifacts for milestones and release > candidates on the download website. I think there are good reasons to > keep the EPP packages around. > > E.g. the 2018-09 SimRel release contains seven p2 repos (M1, M2, M3, > RC1, RC2, and two respins). Only the final release (the last respin) is > relevant AFAICT. This would save 10-15GB disk space per release > depending on the number of respins. > > I'd propose that all repos of a release (e.g. 2021-06) are kept until > the next final release (e.g. 2021-09) has dropped. Everything except the > final release repo (of 2021-06) will then be removed. This would set the > retention time to roughly three months. > > WDYT? > +1. Keeping M* and RC* builds is pointless past GA. > > Regards, > > Fred > > > -- > Frederic Gurr > Release Engineer | Eclipse Foundation Europe GmbH > > Berliner Allee 47, D-64295 Darmstadt > Handelsregister: Darmstadt HRB 92821 > Managing Directors: Gaël Blondelle, Mike Milinkovich > _______________________________________________ > 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
