Re: [cross-project-issues-dev] Simultaneous Release participation and the Eclipse IDE packages

> *All bundles must be signed using the EF's certificate. *Obvious >> exceptions will be made in cases where signing is impossible. >> > >> We will be applying this standard to the next release and for every >> release thereafter. >> >> The means by which the simultaneous release participation rule

Re: [cross-project-issues-dev] Simultaneous Release participation and the Eclipse IDE packages

[cross-posted to epp-dev mailing-list] Hi, That means that the "Eclipse IDE for Rust developers" package should not appear on the https://www.eclipse.org/downloads/packages/ page. To be honest, it's not a big deal, I'll adjust links from Corrosion README so they point to the internal EPP download

Re: [cross-project-issues-dev] Simultaneous Release participation and the Eclipse IDE packages

On Fri, Jan 22, 2021 at 5:23 PM Wayne Beaton < wayne.bea...@eclipse-foundation.org> wrote: > As the recent SolarWinds hack has reminded us, security is everyone's > concern. We owe it to the millions of developers and adopters who use our > technologies to take all reasonable steps to ensure the v

[cross-project-issues-dev] Simultaneous Release participation and the Eclipse IDE packages

As the recent SolarWinds hack has reminded us, security is everyone's concern. We owe it to the millions of developers and adopters who use our technologies to take all reasonable steps to ensure the validity of the software that we distribute. Responsibility to decide which Eclipse IDE packages a

[cross-project-issues-dev] Scheduled upgrade of a build cluster

Hi, We will be doing an upgrade of the new build cluster on January 29th at 13:00 EST. Some Jenkins instances will be restarted (the ones labelled as "okd" on https://ci.eclipse.org). Watch https://www.eclipsestatus.io/incidents/nwc167whsskz?u=jj3b62dj4xzk