[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cross-project-issues-dev] [eclipse.org-planning-council] Neon.3 Update Problems
- From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
- Date: Thu, 30 Mar 2017 20:45:12 +0200
- Delivered-to: email@example.com
> On 30. Mar 2017, at 19:10, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
> I have never seen an announcement from Orbit that service release builds for Orbit got dropped, but that seems to be the current reality, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=509412#c19.
I'm not entirely sure we ever officially had a maintenance/service build story in Orbit. Shouldn't the retention policy keep old bundles in place so that projects referencing those would still consume them during the Neon series?
FWIW, I recall that David did create a "maintenance" branch for a Mars SR back in the days but that was more of an "ad-hoc" thing. I never remember using a maintenance branch in Orbit.
I think there is also another thing to consider. IMHO projects should stop hard-pinning specific 3rd party versions in the feature.xml - at least in the feature they submit into the common repo. This triggers p2 to install multiple versions into packages. We also have projects that update dependencies at different paces. This is concerning from a security perspective. Should we consider something more drastic like target platform filtering when building the packages?