Re: [epp-dev] Moving a package to Java 11 as requirement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [epp-dev] Moving a package to Java 11 as requirement

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Sun, 1 Mar 2020 19:27:35 +0100
Delivered-to: epp-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/epp-dev>
List-help: <mailto:epp-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/epp-dev>, <mailto:epp-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/epp-dev>, <mailto:epp-dev-request@eclipse.org?subject=unsubscribe>

On Fri, Feb 28, 2020 at 9:27 AM Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:

No, it is not OK for the same arguments mentioned before.

Can you please remind those arguments? I'm curious about which ones apply to typical Corrosion target audience.

Also -and without any offense but more to clarify who has influence/authority on EPP project as it's facing a transition-, I'm curious about whether your opinion as Planning Council member but non-EPP committers is to be considered as binding. WDYT?

Follow-Ups:
- Re: [epp-dev] Moving a package to Java 11 as requirement
  - From: Daniel Megert
- Re: [epp-dev] Moving a package to Java 11 as requirement
  - From: Aleksandar Kurtakov

References:
- [epp-dev] Moving a package to Java 11 as requirement
  - From: Mickael Istria
- Re: [epp-dev] Moving a package to Java 11 as requirement
  - From: Andrey Loskutov
- Re: [epp-dev] Moving a package to Java 11 as requirement
  - From: Mickael Istria
- Re: [epp-dev] Moving a package to Java 11 as requirement
  - From: Daniel Megert

Prev by Date: Re: [epp-dev] Update composites for M3
Next by Date: Re: [epp-dev] Moving a package to Java 11 as requirement
Previous by thread: Re: [epp-dev] Moving a package to Java 11 as requirement
Next by thread: Re: [epp-dev] Moving a package to Java 11 as requirement
Index(es):
- Date
- Thread

Breadcrumbs