Re: [cross-project-issues-dev] Simultaneous Release Page 2020-09

2020-09-01 Thread Mickael Istria 
On Mon, Aug 31, 2020 at 1:38 PM Mickael Istria  wrote:

> m2e *might* be 1.16.2 but that depends on a change upstream non-SimRel
> project (LemMinX) that not certain for 2020-09.
>

I confirm m2e will be 1.16.2, as important fix has been made available
upstream
https://projects.eclipse.org/projects/technology.m2e/releases/1.16.2
-- 
Mickael Istria
Eclipse IDE 
developer, for Red Hat Developers 
___
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

Re: [cross-project-issues-dev] Simultaneous Release Page 2020-09

2020-09-01 Thread Nanivadekar, Nikhil J 
Hi Wayne, can you please update Eclipse Collections to 10.4.0?

Thanks,
Nikhil.

From: cross-project-issues-dev-boun...@eclipse.org 
 On Behalf Of Wayne Beaton
Sent: Tuesday, September 1, 2020 1:52 PM
To: Cross project issues 
Subject: Re: [cross-project-issues-dev] Simultaneous Release Page 2020-09

Updated. Thanks.

Wayne

On Tue, Sep 1, 2020 at 2:33 PM Frank Becker (Eclipse) 
mailto:ecli...@frank-becker.de>> wrote:
Hi Wayne,

Mylyn will contribute version 3.25.2.

Cheers

Frank


Am 27.08.2020 um 20:50 schrieb Wayne Beaton 
mailto:wayne.bea...@eclipse-foundation.org>>:

I've created the tracking page for 
2020-09.
 Please have a look to ensure that I've correctly recorded your project's 
participation correctly.

In particular, please make sure that I have the version right. If I've made a 
mistake... please first make sure that you've created a release record for the 
right version and then let me know to update the tracking page to point to that 
version.

If you are contributing a new major or minor release and have not engaged in a 
release review since September 16/2019, then you need to submit your IP Log and 
connect with EMO ASAP to initiate the release review process. Note that you 
only need to submit your IP Log for review if you are required to engage in a 
release review. There's more information in the 
handbook.

Based on messages on this list, both Eclipse Corrosion, Eclipse EMFStore, and 
Eclipse Tools for Cloud Foundry (CFT) have dropped out, so they've been removed 
from the list.

AFAICT, the corrosion.aggrcon file still exists and is not disabled. Also, 
since CFT has dropped out, its aggrcon file should also be removed (not just 
disabled). Can somebody take care of that, please?

Thanks for all your efforts.

Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
Join us at our virtual event: EclipseCon 
2020
 - October 20-22
___
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

___
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


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 
2020
 - October 20-22

The information contained in this e-mail, and any attachment, is confidential 
and is intended solely for the use of the intended recipient. Access, copying 
or re-use of the e-mail or any attachment, or any information contained 
therein, by any other person is not authorized. If you are not the intended 
recipient please return the e-mail to the sender and delete it from your 
computer. Although we attempt to sweep e-mail and attachments for viruses, we 
do not guarantee that either are virus-free and accept no liability for any 
damage sustained as a result of viruses. 

Please refer to https://disclaimer.bnymellon.com/eu.htm for certain disclosures 
relating to European legal entities. We take our data protection and privacy 
responsibilities seriously and our privacy notice explains how we collect, use 
and share personal information in the course of our business activities. It can 
be accessed at the privacy section of  www.bnymellon.com.
___
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

Re: [cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-01 Thread Wayne Beaton 
Right. I forgot about the Eclipse License Feature.

FWIW, I've opened a bug
 to add this to the
Eclipse Project Handbook.

Should (or do) we have this captured in the simultaneous release
documentation?

Wayne

On Tue, Sep 1, 2020 at 5:18 PM Matthias Sohn 
wrote:

> On Tue, Sep 1, 2020 at 10:52 PM Ralph Soika  wrote:
>
>> Hi,
>>
>> in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text
>> seems to be outdated (it is still from the year 2011).
>>
>> Can someone please point me to a page or another eclipse project, where I
>> can see the correct Eclipse license text, so that I can copy the text into
>> my features.properties and license.html artifacts. Especially the text for
>> the feature.properties has a curious formatting. So I am looking for a
>> features.properties file where I can copy this formatting to avoid breaking
>> the text formatting at some line where I should not do so.
>>
>> we use the eclipse license feature [1] e.g. here in the egit feature [2].
> The version of the license feature is defined in the target platform we
> use [3].
> In feature.properties we use [4]. If there is a new version of the license
> we
> update the version of the license feature we include in the target
> platform.
>
> [1]
> https://git.eclipse.org/r/plugins/gitiles/cbi/org.eclipse.license/+/refs/heads/master
> [2]
> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.xml#8
> [3]
> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit.target/egit-4.16-staging.target#25
> [4]
> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.properties#22
>
>
> -Matthias
> ___
> 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
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020
 - October 20-22
___
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

Re: [cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-01 Thread Matthias Sohn 
On Tue, Sep 1, 2020 at 10:52 PM Ralph Soika  wrote:

> Hi,
>
> in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text
> seems to be outdated (it is still from the year 2011).
>
> Can someone please point me to a page or another eclipse project, where I
> can see the correct Eclipse license text, so that I can copy the text into
> my features.properties and license.html artifacts. Especially the text for
> the feature.properties has a curious formatting. So I am looking for a
> features.properties file where I can copy this formatting to avoid breaking
> the text formatting at some line where I should not do so.
>
> we use the eclipse license feature [1] e.g. here in the egit feature [2].
The version of the license feature is defined in the target platform we use
[3].
In feature.properties we use [4]. If there is a new version of the license
we
update the version of the license feature we include in the target platform.

[1]
https://git.eclipse.org/r/plugins/gitiles/cbi/org.eclipse.license/+/refs/heads/master
[2]
https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.xml#8
[3]
https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit.target/egit-4.16-staging.target#25
[4]
https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.properties#22


-Matthias
___
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

Re: [cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-01 Thread Wayne Beaton 
There's pointers in the handbook section on the topic.

https://www.eclipse.org/projects/handbook/#legaldoc-plugins

There's also a pointer in the simultaneous release participation
requirements

.

I assume/hope that you're updating to EPL-2.0 while you're at it. Please
send a note to e...@eclipse.org to inform them of the change so that we can
update the project's metadata.

HTH,

Wayne

On Tue, Sep 1, 2020 at 4:52 PM Ralph Soika  wrote:

> Hi,
>
> in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text
> seems to be outdated (it is still from the year 2011).
>
> Can someone please point me to a page or another eclipse project, where I
> can see the correct Eclipse license text, so that I can copy the text into
> my features.properties and license.html artifacts. Especially the text for
> the feature.properties has a curious formatting. So I am looking for a
> features.properties file where I can copy this formatting to avoid breaking
> the text formatting at some line where I should not do so.
>
> Thanks for help
>
> Ralph
>
>
>
>
> --
>
> *Imixs Software Solutions GmbH*
> *Web:* www.imixs.com *Phone:* +49 (0)89-452136 16
> *Office:* Agnes-Pockels-Bogen 1, 80992 München
> Registergericht: Amtsgericht Muenchen, HRB 136045
> Geschaeftsführer: Gaby Heinle u. Ralph Soika
>
> *Imixs* is an open source company, read more: www.imixs.org
> ___
> 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
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020
 - October 20-22
___
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

[cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-01 Thread Ralph Soika 

Hi,

in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text 
seems to be outdated (it is still from the year 2011).


Can someone please point me to a page or another eclipse project, where 
I can see the correct Eclipse license text, so that I can copy the text 
into my features.properties and license.html artifacts. Especially the 
text for the feature.properties has a curious formatting. So I am 
looking for a features.properties file where I can copy this formatting 
to avoid breaking the text formatting at some line where I should not do 
so.


Thanks for help

Ralph




--

*Imixs Software Solutions GmbH*
*Web:* www.imixs.com  *Phone:* +49 (0)89-452136 16
*Office:* Agnes-Pockels-Bogen 1, 80992 München
Registergericht: Amtsgericht Muenchen, HRB 136045
Geschaeftsführer: Gaby Heinle u. Ralph Soika

*Imixs* is an open source company, read more: www.imixs.org 



###
# Copyright (c) 2011, 2012, 2013, 2014 Red Hat, Inc. 
# All rights reserved. 
# This program is made available under the terms of the 
# Eclipse Public License v1.0 which accompanies this distribution, 
# and is available at http://www.eclipse.org/legal/epl-v10.html 
#
# Contributors: 
# Red Hat, Inc. - initial API and implementation 
###
copyright=Copyright (c) 2011-2016 Red Hat, Inc. and others. \
All rights reserved. This program and the accompanying materials \
are made available under the terms of the Eclipse Public License v1.0 \
which accompanies this distribution, and is available at

providerName=Eclipse.org

# "licenseURL" property - URL of the "Feature License"
# do not translate value - just change to point to a locale-specific HTML page
licenseURL=license.html

# "license" property - text of the "Feature Update License"
# should be plain text version of license agreement pointed to be "licenseURL"
license=\
Eclipse Foundation Software User Agreement\n\
February 1, 2011\n\
\n\
Usage Of Content\n\
\n\
THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION 
AND/OR\n\
OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
NOTICES INDICATED OR REFERENCED BELOW.  BY USING THE CONTENT, YOU\n\
AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
OR NOTICES INDICATED OR REFERENCED BELOW.  IF YOU DO NOT AGREE TO THE\n\
TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
\n\
Applicable Licenses\n\
\n\
Unless otherwise indicated, all Content made available by the\n\
Eclipse Foundation is provided to you under the terms and conditions of\n\
the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
provided with this Content and is also available at 
http://www.eclipse.org/legal/epl-v10.html.\n\
For purposes of the EPL, "Program" will mean the Content.\n\
\n\
Content includes, but is not limited to, source code, object code,\n\
documentation and other files maintained in the Eclipse Foundation source 
code\n\
repository ("Repository") in software modules ("Modules") and made available\n\
as downloadable archives ("Downloads").\n\
\n\
   - Content may be structured and packaged into modules to facilitate 
delivering,\n\
 extending, and upgrading the Content. Typical modules may include 
plug-ins ("Plug-ins"),\n\
 plug-in fragments ("Fragments"), and features ("Features").\n\
   - Each Plug-in or Fragment may be packaged as a sub-directory or JAR 
(Java(TM) ARchive)\n\
 in a directory named "plugins".\n\
   - A Feature is a bundle of one or more Plug-ins and/or Fragments and 
associated material.\n\
 Each Feature may be packaged as a sub-directory in a directory named 
"features".\n\
 Within a Feature, files named "feature.xml" may contain a list of the 
names and version\n\
 numbers of the Plug-ins and/or Fragments associated with that 
Feature.\n\
   - Features may also include other Features ("Included Features"). Within 
a Feature, files\n\
 named "feature.xml" may contain a list of the names and version 
numbers of Included Features.\n\
\n\
The terms and conditions governing Plug-ins and Fragments should be\n\
contained in files named "about.html" ("Abouts"). The terms and\n\
conditions governing Features and Included Features should be contained\n\
in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
Licenses may be located in any directory of a Download or Module\n\
including, but not limited to the following locations:\n\
\n\

Re: [cross-project-issues-dev] Corrosion dropping from SimRel

2020-09-01 Thread Mickael Istria 
On Tue, Sep 1, 2020 at 7:53 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> Somebody will correct me if I'm wrong, but AFAIK it a requirement for
> inclusion in an EPP package is participation in the simultaneous release.
> [...]
> Per EPP/How to create a package
> :
>
> Packages must only contain code from Eclipse projects from the
>> Simultaneous Release
>
>
SimRel is not a requirement for EPP any more, this was clarified with
Planning Council earlier this year.
The documentation needs to be updated, we'll look at it soon.


> The simultaneous release participation requirements are an important part
> of the quality controls around the packages.
>

That's arguable and you recently mentioned in another that you don't like
discussions that argue about the value of SimRel ;)

Independent of this, according to my records, Eclipse Corrosion is overdue
> for a Release Review. Please initiate one immediately.
>

I'll take care of it soon. In the worst case, it's totally fine if we ship
the previous 0.4.2 version of Corrosion in the upcoming SimRel. But a 0.4.3
would indeed be better.
___
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

Re: [cross-project-issues-dev] Simultaneous Release Page 2020-09

2020-09-01 Thread Wayne Beaton 
Updated. Thanks.

Wayne

On Tue, Sep 1, 2020 at 2:33 PM Frank Becker (Eclipse) <
ecli...@frank-becker.de> wrote:

> Hi Wayne,
>
> Mylyn will contribute version 3.25.2.
>
> Cheers
>
> Frank
>
> Am 27.08.2020 um 20:50 schrieb Wayne Beaton <
> wayne.bea...@eclipse-foundation.org>:
>
> I've created the tracking page for 2020-09
> . Please have a look to
> ensure that I've correctly recorded your project's participation correctly.
>
> In particular, please make sure that I have the version right. If I've
> made a mistake... please first make sure that you've created a release
> record for the right version and then let me know to update the tracking
> page to point to that version.
>
> If you are contributing a new major or minor release and have not engaged
> in a release review since September 16/2019, then you need to submit your
> IP Log and connect with EMO ASAP to initiate the release review process.
> Note that you only need to submit your IP Log for review if you are
> required to engage in a release review. There's more information in the
> handbook .
>
> Based on messages on this list, both Eclipse Corrosion, Eclipse EMFStore,
> and Eclipse Tools for Cloud Foundry (CFT) have dropped out, so they've been
> removed from the list.
>
> *AFAICT, the corrosion.aggrcon file still exists and is not disabled.* Also,
> since CFT has dropped out, its aggrcon file should also be removed (not
> just disabled). Can somebody take care of that, please?
>
> Thanks for all your efforts.
>
> Wayne
> --
> Wayne Beaton
> Director of Open Source Projects | Eclipse Foundation, Inc.
> Join us at our virtual event: EclipseCon 2020
>  - October 20-22
> ___
> 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
>
>
> ___
> 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
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020
 - October 20-22
___
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

Re: [cross-project-issues-dev] Simultaneous Release Page 2020-09

2020-09-01 Thread Frank Becker (Eclipse) 
Hi Wayne,

Mylyn will contribute version 3.25.2.

Cheers

Frank

> Am 27.08.2020 um 20:50 schrieb Wayne Beaton 
> :
> 
> I've created the tracking page for 2020-09 
> . Please have a look to ensure 
> that I've correctly recorded your project's participation correctly.
> 
> In particular, please make sure that I have the version right. If I've made a 
> mistake... please first make sure that you've created a release record for 
> the right version and then let me know to update the tracking page to point 
> to that version.
> 
> If you are contributing a new major or minor release and have not engaged in 
> a release review since September 16/2019, then you need to submit your IP Log 
> and connect with EMO ASAP to initiate the release review process. Note that 
> you only need to submit your IP Log for review if you are required to engage 
> in a release review. There's more information in the handbook 
> .
> 
> Based on messages on this list, both Eclipse Corrosion, Eclipse EMFStore, and 
> Eclipse Tools for Cloud Foundry (CFT) have dropped out, so they've been 
> removed from the list. 
> 
> AFAICT, the corrosion.aggrcon file still exists and is not disabled. Also, 
> since CFT has dropped out, its aggrcon file should also be removed (not just 
> disabled). Can somebody take care of that, please?
> 
> Thanks for all your efforts.
> 
> Wayne
> -- 
> Wayne Beaton
> Director of Open Source Projects | Eclipse Foundation, Inc.
> Join us at our virtual event: EclipseCon 2020 
>  - October 20-22
> ___
> 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

___
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

Re: [cross-project-issues-dev] Corrosion dropping from SimRel

2020-09-01 Thread Wayne Beaton 
Sorry for just noticing this...

Somebody will correct me if I'm wrong, but AFAIK it a requirement for
inclusion in an EPP package is participation in the simultaneous release.
The simultaneous release participation requirements are an important part
of the quality controls around the packages.

Per EPP/How to create a package
:

Packages must only contain code from Eclipse projects from the Simultaneous
> Release


Independent of this, according to my records, Eclipse Corrosion is overdue
for a Release Review. Please initiate one immediately.

Wayne


On Fri, Aug 21, 2020 at 4:00 AM Mickael Istria  wrote:

> Hi all,
>
> Corrosion is leaving SimRel. I'll make the actual change in a few minutes.
> Corrosion remains an active project, with decent maintenance (more would
> be better and the project is open to new contributors ;) ), and will still
> be included in the "Eclipse IDE for Rust developers" EPP package.
> The reason behind that change is that SimRel was identified by its
> contributors in mailing-list discussions as a non-profitable extra-step for
> Corrosion, whose main target for downstream consumption are EPP packages.
>
> Cheers,
> --
> Mickael Istria
> Eclipse IDE 
> developer, for Red Hat Developers 
> ___
> 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
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020
 - October 20-22
___
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

Re: [cross-project-issues-dev] JDK on JIPP Instance

2020-09-01 Thread Frederic Gurr 
Hi,

Lorenzo does not have administrator rights on the EMF Parsley JIPP, so
he had to open a Bugzilla issue.

Regards,

Fred

On 31.08.20 22:11, Ed Merks wrote:
> Lorenzo,
> 
> I don't know if you got help on the Bugzilla, but you can configure this
> yourself via Manage Jenkins -> Global Tools Configuration -> JDK
> installations... adding jdk11-latest for
> /shared/common/java/oracle/jdk-11_x64
> 
> I had to do that for the Oomph and EMF instances.
> 
> Regards,
> Ed
> 
> On 31.08.2020 13:27, Lorenzo Bettini wrote:
>> Hi
>>
>> For EMF Parsley we have to do the port to JDK 11 but on our JIPP only
>> up to JDK 9 is
>> selectable... do we have to require that explicitly or can we get
>> access to JDK 11
>> somehow? In the meantime I opened a bug against Community->CI-Jenkins...
>>
>> thanks in advance
>> Lorenzo
>>
> ___
> 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

-- 
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Annastr. 46, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Gaël Blondelle
___
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