Re: [cross-project-issues-dev] Eclipse IDE 2024-06 Project Participation Page

2024-05-29 Thread Eike Stepper via cross-project-issues-dev

Hi Wayne,

CDO will contribute 4.27 (not 4.26).

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Am 22.05.2024 um 23:56 schrieb Wayne Beaton via cross-project-issues-dev:

Greetings folks!

I've assembled the release information for participating projects here 
.

Note that the list of projects reflects our long time practice of only including projects whose teams are actively 
participating in the simultaneous release. If you look hard enough, you'll notice that projects that have been 
"sponsored in" by participating projects are absent from the list. This is per the requirements. I expect that these 
requirements will change in some future release.


A lot of the releases are quite old, and based on the activity in the simrel.build 
 repository,  at least a few projects need to create some release 
records, and some may need to engage in a progress review (I've done my usual thing of making by best guess based on 
the release records in the system).


If your project is contributing a different release than what you see here, please ensure that you've created a 
release record , and let me know. If your project has 
not engaged in a progress (or release) review  in more 
than one year, please engage with the EMO ASAP to schedule a review.


Be sure to set the New and Noteworthy URL in your release record: it is through this relationship that we build the 
aggregate N


Please make sure that you've made your best effort to engage in the IP Due Diligence Process for all third party 
content before you engage with the EMO for review. Bear in mind that you should be engaging in the IP Due Diligence 
Process  on an ongoing basis and that all releases 
(regardless of whether or not they correspond with a progress or release review) must only contain content that has 
been vetted through the due diligence process. With the Eclipse Dash License Tool 
 and the ability to use it to automatically create review requests, it 
should be /easier than ever/ before to engage (the README has extensive information on how to engage, and does include 
some pointers for using it with Eclipse Tycho -based builds). 
Connect with the EMO if you need assistance.


Here are some things that I've observed:

Eclipse Client Platform has been removed.

The aggrcon files for the following projects are disabled; if any of these projects are dropping from the release, 
please let me know:


  * Eclipse Xpand
  * Eclipse BPMN2 Modeler Project
  * Eclipse RCPTT

Let me know what I've missed.

Thanks,

Wayne
--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation

My working day may not be your working day! Please don’t feel obliged to read or reply to this e-mail outside of your 
normal working hours.



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, 
visithttps://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] Eclipse IDE 2024-06 Project Participation Page

2024-05-27 Thread Patrick Tasse via cross-project-issues-dev
Hi,

Eclipse Trace Compass will contribute
https://projects.eclipse.org/projects/tools.tracecompass/releases/10.0.0
Eclipse SWTBot will contribute
https://projects.eclipse.org/projects/technology.swtbot/releases/4.2.0

Thanks,
Patrick

On Wed, May 22, 2024 at 5:56 PM Wayne Beaton via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> wrote:

> Greetings folks!
>
> I've assembled the release information for participating projects here
> .
>
> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build 
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> , and
> let me know. If your project has not engaged in a progress (or release)
> review  in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
>  on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool  and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> -based builds).
> Connect with the EMO if you need assistance.
>
> Here are some things that I've observed:
>
> Eclipse Client Platform has been removed.
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> 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] Eclipse IDE 2024-06 Project Participation Page

2024-05-24 Thread Edward Willink via cross-project-issues-dev
OCL contributes 2024-06 (6.21.0) 



QVTd contributes 2024-06 (0.32.0) 

___
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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Matthias Sohn via cross-project-issues-dev
On Thu, May 23, 2024 at 10:42 PM Wayne Beaton via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> wrote:

> I have applied all of the updates. There's an anomaly in the system
> related to the recent upgrade of the PMI that required a little more
> mechanical work than usual to apply these updates, so there is some chance
> that I may have messed something up. If you notice something, let me know.
>

You missed to update JGit which will ship 6.10.0 not 6.9.0

AFAICT (based on what I'm seeing in the simrel.build Git repository), this
> release marks the return of the Eclipse Papyrus project to the simultaneous
> release. Welcome back.
>
> Please let me know if there are any other issues.
>
> If you require a review, please reach out to the EMO.
>
> Wayne
>
> On Wed, 22 May 2024 at 17:56, Wayne Beaton <
> wayne.bea...@eclipse-foundation.org> wrote:
>
>> Greetings folks!
>>
>> I've assembled the release information for participating projects here
>> .
>>
>> Note that the list of projects reflects our long time practice of only
>> including projects whose teams are actively participating in the
>> simultaneous release. If you look hard enough, you'll notice that projects
>> that have been "sponsored in" by participating projects are absent from the
>> list. This is per the requirements. I expect that these requirements will
>> change in some future release.
>>
>> A lot of the releases are quite old, and based on the activity in the
>> simrel.build 
>> repository,  at least a few projects need to create some release records,
>> and some may need to engage in a progress review (I've done my usual thing
>> of making by best guess based on the release records in the system).
>>
>> If your project is contributing a different release than what you see
>> here, please ensure that you've created a release record
>> , and
>> let me know. If your project has not engaged in a progress (or release)
>> review  in
>> more than one year, please engage with the EMO ASAP to schedule a review.
>>
>> Be sure to set the New and Noteworthy URL in your release record: it is
>> through this relationship that we build the aggregate N
>>
>> Please make sure that you've made your best effort to engage in the IP
>> Due Diligence Process for all third party content before you engage with
>> the EMO for review. Bear in mind that you should be engaging in the IP
>> Due Diligence Process
>>  on an
>> ongoing basis and that all releases (regardless of whether or not they
>> correspond with a progress or release review) must only contain content
>> that has been vetted through the due diligence process. With the Eclipse
>> Dash License Tool  and the
>> ability to use it to automatically create review requests, it should be 
>> *easier
>> than ever* before to engage (the README has extensive information on how
>> to engage, and does include some pointers for using it with Eclipse Tycho
>> -based builds).
>> Connect with the EMO if you need assistance.
>>
>> Here are some things that I've observed:
>>
>> Eclipse Client Platform has been removed.
>>
>> The aggrcon files for the following projects are disabled; if any of
>> these projects are dropping from the release, please let me know:
>>
>>- Eclipse Xpand
>>- Eclipse BPMN2 Modeler Project
>>- Eclipse RCPTT
>>
>> Let me know what I've missed.
>>
>> Thanks,
>>
>> Wayne
>> --
>>
>> Wayne Beaton
>>
>> Director of Open Source Projects | Eclipse Foundation
>>
>>
>> My working day may not be your working day! Please don’t feel obliged to
>> read or reply to this e-mail outside of your normal working hours.
>>
>
>
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> 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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Wayne Beaton via cross-project-issues-dev
I have applied all of the updates. There's an anomaly in the system related
to the recent upgrade of the PMI that required a little more mechanical
work than usual to apply these updates, so there is some chance that I may
have messed something up. If you notice something, let me know.

AFAICT (based on what I'm seeing in the simrel.build Git repository), this
release marks the return of the Eclipse Papyrus project to the simultaneous
release. Welcome back.

Please let me know if there are any other issues.

If you require a review, please reach out to the EMO.

Wayne

On Wed, 22 May 2024 at 17:56, Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> Greetings folks!
>
> I've assembled the release information for participating projects here
> .
>
> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build 
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> , and
> let me know. If your project has not engaged in a progress (or release)
> review  in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
>  on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool  and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> -based builds).
> Connect with the EMO if you need assistance.
>
> Here are some things that I've observed:
>
> Eclipse Client Platform has been removed.
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation


My working day may not be your working day! Please don’t feel obliged to
read or reply to this e-mail outside of your normal working hours.
___
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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Patrick Ziegler via cross-project-issues-dev

WindowBuilder contributes 1.16 for the 2024-06.

The release record has already been created some time ago. Did I miss 
some settings that caused it to slip through?


Many regards,

Patrick


On 22.05.24 23:56, Wayne Beaton via cross-project-issues-dev wrote:

Greetings folks!

I've assembled the release information for participating projects here 
.


Note that the list of projects reflects our long time practice of only 
including projects whose teams are actively participating in the 
simultaneous release. If you look hard enough, you'll notice that 
projects that have been "sponsored in" by participating projects are 
absent from the list. This is per the requirements. I expect that 
these requirements will change in some future release.


A lot of the releases are quite old, and based on the activity in the 
simrel.build  
repository,  at least a few projects need to create some release 
records, and some may need to engage in a progress review (I've done 
my usual thing of making by best guess based on the release records in 
the system).


If your project is contributing a different release than what you see 
here, please ensure that you've created a release record 
, and 
let me know. If your project has not engaged in a progress (or 
release) review 
 in more 
than one year, please engage with the EMO ASAP to schedule a review.


Be sure to set the New and Noteworthy URL in your release record: it 
is through this relationship that we build the aggregate N


Please make sure that you've made your best effort to engage in the IP 
Due Diligence Process for all third party content before you engage 
with the EMO for review. Bear in mind that you should be engaging in 
the IP Due Diligence Process 
 on an 
ongoing basis and that all releases (regardless of whether or not they 
correspond with a progress or release review) must only contain 
content that has been vetted through the due diligence process. With 
the Eclipse Dash License Tool 
 and the ability to use it 
to automatically create review requests, it should be /easier than 
ever/ before to engage (the README has extensive information on how to 
engage, and does include some pointers for using it with Eclipse Tycho 
-based 
builds). Connect with the EMO if you need assistance.


Here are some things that I've observed:

Eclipse Client Platform has been removed.

The aggrcon files for the following projects are disabled; if any of 
these projects are dropping from the release, please let me know:


  * Eclipse Xpand
  * Eclipse BPMN2 Modeler Project
  * Eclipse RCPTT

Let me know what I've missed.

Thanks,

Wayne
--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation

My working day may not be your working day! Please don’t feel obliged 
to read or reply to this e-mail outside of your normal working hours.



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, 
visithttps://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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Dawid Pakuła via cross-project-issues-dev
  
Hi Wayne,
  
​
  
​for Eclipse DLTK it will be 6.4.1 (just for API compatibility)
  
​
  
​https://projects.eclipse.org/projects/technology.dltk/releases/6.4.1
  
​
  
​Thanks
  
​
  
  
  
​--
  
​Dawid Pakuła
  
​
  
  
  
On May 22 2024, at 11:56 PM, Wayne Beaton via cross-project-issues-dev  
  wrote:
  
>   
>   
> Greetings folks!
>   
>
>   
> I've assembled the release information for participating projects  here 
> (https://projects.eclipse.org/releases/2024-06).   
>   
>
>   
>   
> Note that the list of projects reflects our long time practice of only 
> including projects whose teams are actively participating in the simultaneous 
> release. If you look hard enough, you'll notice that projects that have been 
> "sponsored in" by participating projects are absent from the list. This is 
> per the requirements. I expect that these requirements will change in some 
> future release.
>   
>   
>
>   
> A lot of the releases are quite old, and based on the activity in the  
> simrel.build (https://github.com/eclipse-simrel/simrel.build)  repository,
> at least a few projects need to create some release records, and some may 
> need to engage in a progress review (I've done my usual thing of making by 
> best guess based on the release records in the system).
>   
>
>   
> If your project is contributing a different release than what you see here, 
> please ensure that you've created a  release record 
> (https://www.eclipse.org/projects/handbook/#pmi-commands-release), and let me 
> know. If your project has not engaged in a  progress (or release) review 
> (https://www.eclipse.org/projects/handbook/#progress-review)  in more than 
> one year, please engage with the EMO ASAP to schedule a review.
>   
>
>   
>   
> Be sure to set the New and Noteworthy URL in your release record: it is 
> through this relationship that we build the aggregate N
>   
>   
>
>   
> Please make sure that you've made your best effort to engage in the IP Due 
> Diligence Process for all third party content before you engage with the EMO 
> for review. Bear in mind that you should be engaging in the  IP Due Diligence 
> Process (https://www.eclipse.org/projects/handbook/#ip-third-party)  on an 
> ongoing basis and that all releases (regardless of whether or not they 
> correspond with a progress or release review) must only contain content that 
> has been vetted through the due diligence process. With the  Eclipse Dash 
> License Tool (https://github.com/eclipse/dash-licenses)  and the ability to 
> use it to automatically create review requests, it should be  easier than 
> ever  before to engage (the README has extensive information on how to 
> engage, and does include some pointers for using it with  Eclipse Tycho 
> (https://github.com/eclipse/dash-licenses#eclipse-tycho)-based builds). 
> Connect with the EMO if you need assistance.
>   
>
>   
>   
> Here are some things that I've observed:
>   
>   
>
>   
> Eclipse Client Platform has been removed.
>   
>
>   
> The aggrcon files for the following projects are disabled; if any of these 
> projects are dropping from the release, please let me know:
>   
>   
>   
> Eclipse Xpand
>   
>   
>   
> Eclipse BPMN2 Modeler Project
>   
>   
>   
> Eclipse RCPTT
>   
>   
>   
> Let me know what I've missed.
>   
>
>   
> Thanks,
>   
>
>   
> Wayne
>   
> --
>   
>   
>   
>   
>   
>   
>   
>   
>   
> Wayne Beaton
>   
> Director of Open Source Projects |   Eclipse Foundation
>   
>
>   
>   
> My working day may not be your working day! Please don’t feel obliged to read 
> or reply to this e-mail outside of your normal working hours.
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
> ___
>   
> 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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Markus Knauer via cross-project-issues-dev
Hi Wayne,

for Eclipse RAP it will be version 3.29.

Thanks and regards
Markus

On Thu, 23 May 2024 at 11:08, DEVILLE Pauline via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> wrote:

> Hello Wayne and all,
>
>
>
> Papyrus will also participate to 2024-06 and will contribute a 6.7.0
> version :
> https://projects.eclipse.org/projects/modeling.mdt.papyrus/releases/6.7.0
>
>
>
> Best regards,
>
> Pauline DEVILLE
>
>
>
> *De :* cross-project-issues-dev <
> cross-project-issues-dev-boun...@eclipse.org> *De la part de* Wayne
> Beaton via cross-project-issues-dev
> *Envoyé :* mercredi 22 mai 2024 23:56
> *À :* Cross project issues 
> *Cc :* Wayne Beaton 
> *Objet :* [cross-project-issues-dev] Eclipse IDE 2024-06 Project
> Participation Page
>
>
>
> Greetings folks!
>
>
>
> I've assembled the release information for participating projects here
> <https://projects.eclipse.org/releases/2024-06>.
>
>
>
> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
>
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build <https://github.com/eclipse-simrel/simrel.build>
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
>
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> <https://www.eclipse.org/projects/handbook/#pmi-commands-release>, and
> let me know. If your project has not engaged in a progress (or release)
> review <https://www.eclipse.org/projects/handbook/#progress-review> in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
>
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N
>
>
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
> <https://www.eclipse.org/projects/handbook/#ip-third-party> on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool <https://github.com/eclipse/dash-licenses> and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> <https://github.com/eclipse/dash-licenses#eclipse-tycho>-based builds).
> Connect with the EMO if you need assistance.
>
>
>
> Here are some things that I've observed:
>
>
>
> Eclipse Client Platform has been removed.
>
>
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
>
>
> Thanks,
>
>
>
> Wayne
>
> --
>
> *Wayne Beaton*
>
> *Director of Open Source Projects | **Eclipse Foundation*
>
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> 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
>


-- 

###
EclipseSource Group
Telefon: +49 721 664733-0 (UTC +1)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
___
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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread DEVILLE Pauline via cross-project-issues-dev
Hello Wayne and all,

Papyrus will also participate to 2024-06 and will contribute a 6.7.0 version : 
https://projects.eclipse.org/projects/modeling.mdt.papyrus/releases/6.7.0

Best regards,
Pauline DEVILLE

De : cross-project-issues-dev  De 
la part de Wayne Beaton via cross-project-issues-dev
Envoyé : mercredi 22 mai 2024 23:56
À : Cross project issues 
Cc : Wayne Beaton 
Objet : [cross-project-issues-dev] Eclipse IDE 2024-06 Project Participation 
Page

Greetings folks!

I've assembled the release information for participating projects 
here<https://projects.eclipse.org/releases/2024-06>.

Note that the list of projects reflects our long time practice of only 
including projects whose teams are actively participating in the simultaneous 
release. If you look hard enough, you'll notice that projects that have been 
"sponsored in" by participating projects are absent from the list. This is per 
the requirements. I expect that these requirements will change in some future 
release.

A lot of the releases are quite old, and based on the activity in the 
simrel.build<https://github.com/eclipse-simrel/simrel.build> repository,  at 
least a few projects need to create some release records, and some may need to 
engage in a progress review (I've done my usual thing of making by best guess 
based on the release records in the system).

If your project is contributing a different release than what you see here, 
please ensure that you've created a release 
record<https://www.eclipse.org/projects/handbook/#pmi-commands-release>, and 
let me know. If your project has not engaged in a progress (or release) 
review<https://www.eclipse.org/projects/handbook/#progress-review> in more than 
one year, please engage with the EMO ASAP to schedule a review.

Be sure to set the New and Noteworthy URL in your release record: it is through 
this relationship that we build the aggregate N

Please make sure that you've made your best effort to engage in the IP Due 
Diligence Process for all third party content before you engage with the EMO 
for review. Bear in mind that you should be engaging in the IP Due Diligence 
Process<https://www.eclipse.org/projects/handbook/#ip-third-party> on an 
ongoing basis and that all releases (regardless of whether or not they 
correspond with a progress or release review) must only contain content that 
has been vetted through the due diligence process. With the Eclipse Dash 
License Tool<https://github.com/eclipse/dash-licenses> and the ability to use 
it to automatically create review requests, it should be easier than ever 
before to engage (the README has extensive information on how to engage, and 
does include some pointers for using it with Eclipse 
Tycho<https://github.com/eclipse/dash-licenses#eclipse-tycho>-based builds). 
Connect with the EMO if you need assistance.

Here are some things that I've observed:

Eclipse Client Platform has been removed.

The aggrcon files for the following projects are disabled; if any of these 
projects are dropping from the release, please let me know:

  *   Eclipse Xpand
  *   Eclipse BPMN2 Modeler Project
  *   Eclipse RCPTT
Let me know what I've missed.

Thanks,

Wayne
--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation



My working day may not be your working day! Please don’t feel obliged to read 
or reply to this e-mail outside of your normal working hours.
___
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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Alexander Fedorov via cross-project-issues-dev

Hello Wayne and All,

* Eclipse Passage will contribute 3.0.0 to SimRel 2024-06 
https://projects.eclipse.org/projects/technology.passage/releases/3.0.0


* Eclipse Mylyn will contribute 4.3.0 to SimRel 2024-06 
https://projects.eclipse.org/projects/tools.mylyn/releases/4.3.0

(sorry, there was no release record earlier)

Regards,
AF

23.05.2024 0:56, Wayne Beaton via cross-project-issues-dev пишет:

Greetings folks!

I've assembled the release information for participating projects here 
.


Note that the list of projects reflects our long time practice of only 
including projects whose teams are actively participating in the 
simultaneous release. If you look hard enough, you'll notice that 
projects that have been "sponsored in" by participating projects are 
absent from the list. This is per the requirements. I expect that 
these requirements will change in some future release.


A lot of the releases are quite old, and based on the activity in the 
simrel.build  
repository,  at least a few projects need to create some release 
records, and some may need to engage in a progress review (I've done 
my usual thing of making by best guess based on the release records in 
the system).


If your project is contributing a different release than what you see 
here, please ensure that you've created a release record 
, and 
let me know. If your project has not engaged in a progress (or 
release) review 
 in more 
than one year, please engage with the EMO ASAP to schedule a review.


Be sure to set the New and Noteworthy URL in your release record: it 
is through this relationship that we build the aggregate N


Please make sure that you've made your best effort to engage in the IP 
Due Diligence Process for all third party content before you engage 
with the EMO for review. Bear in mind that you should be engaging in 
the IP Due Diligence Process 
 on an 
ongoing basis and that all releases (regardless of whether or not they 
correspond with a progress or release review) must only contain 
content that has been vetted through the due diligence process. With 
the Eclipse Dash License Tool 
 and the ability to use it 
to automatically create review requests, it should be /easier than 
ever/ before to engage (the README has extensive information on how to 
engage, and does include some pointers for using it with Eclipse Tycho 
-based 
builds). Connect with the EMO if you need assistance.


Here are some things that I've observed:

Eclipse Client Platform has been removed.

The aggrcon files for the following projects are disabled; if any of 
these projects are dropping from the release, please let me know:


  * Eclipse Xpand
  * Eclipse BPMN2 Modeler Project
  * Eclipse RCPTT

Let me know what I've missed.

Thanks,

Wayne
--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation


My working day may not be your working day! Please don’t feel obliged 
to read or reply to this e-mail outside of your normal working hours.



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, 
visithttps://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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Pierre-Charles David via cross-project-issues-dev

Le 22/05/2024 à 23:56, Wayne Beaton via cross-project-issues-dev a écrit :

Greetings folks!

I've assembled the release information for participating projects here 
.


A lot of the releases are quite old, and based on the activity in the 
simrel.build  
repository,  at least a few projects need to create some release 
records, and some may need to engage in a progress review (I've done 
my usual thing of making by best guess based on the release records in 
the system).


If your project is contributing a different release than what you see 
here, please ensure that you've created a release record 
, and 
let me know.


- Ecore Tools will contribute version 3.5.1 (instead of 3.5.0)
- GMF Runtime will contribute version 1.16.4 (instead of 1.16.2)
- Sirius Desktop will contribute version 7.4.0, same as in 2024-03 
(version 7.4.1 is late)


I've updated/completed the corresponding release records.

___
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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Laurent Goubet via cross-project-issues-dev

Hello,

There were missing records for Acceleo and EMF Compare.

Acceleo will release version 3.7.16

EMF Compare will release 3.3.24

Thanks,
Laurent

Le 22/05/2024 à 23:56, Wayne Beaton via cross-project-issues-dev a écrit :

Greetings folks!

I've assembled the release information for participating projects here 
.


Note that the list of projects reflects our long time practice of only 
including projects whose teams are actively participating in the 
simultaneous release. If you look hard enough, you'll notice that 
projects that have been "sponsored in" by participating projects are 
absent from the list. This is per the requirements. I expect that 
these requirements will change in some future release.


A lot of the releases are quite old, and based on the activity in the 
simrel.build  
repository,  at least a few projects need to create some release 
records, and some may need to engage in a progress review (I've done 
my usual thing of making by best guess based on the release records in 
the system).


If your project is contributing a different release than what you see 
here, please ensure that you've created a release record 
, and 
let me know. If your project has not engaged in a progress (or 
release) review 
 in more 
than one year, please engage with the EMO ASAP to schedule a review.


Be sure to set the New and Noteworthy URL in your release record: it 
is through this relationship that we build the aggregate N


Please make sure that you've made your best effort to engage in the IP 
Due Diligence Process for all third party content before you engage 
with the EMO for review. Bear in mind that you should be engaging in 
the IP Due Diligence Process 
 on an 
ongoing basis and that all releases (regardless of whether or not they 
correspond with a progress or release review) must only contain 
content that has been vetted through the due diligence process. With 
the Eclipse Dash License Tool 
 and the ability to use it 
to automatically create review requests, it should be /easier than 
ever/ before to engage (the README has extensive information on how to 
engage, and does include some pointers for using it with Eclipse Tycho 
-based 
builds). Connect with the EMO if you need assistance.


Here are some things that I've observed:

Eclipse Client Platform has been removed.

The aggrcon files for the following projects are disabled; if any of 
these projects are dropping from the release, please let me know:


  * Eclipse Xpand
  * Eclipse BPMN2 Modeler Project
  * Eclipse RCPTT

Let me know what I've missed.

Thanks,

Wayne
--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation

My working day may not be your working day! Please don’t feel obliged 
to read or reply to this e-mail outside of your normal working hours.



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, 
visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

--

*Laurent Goubet*
Consultant
+33 2 51 13 51 42



7 Boulevard Ampère - Carquefou - France
*obeo.fr*  | *twitter* 
 | *linkedin* 

___
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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Alois Zoitl via cross-project-issues-dev
Hi Wayne,

On Wed, 2024-05-22 at 17:56 -0400, Wayne Beaton via cross-project-
issues-dev wrote:
> Greetings folks!
> 
> I've assembled the release information for participating projects
> here. 

thx for the reminder. Eclipse GEF Classic will contribute 3.20.0. I
just created the release record:
https://projects.eclipse.org/projects/tools.gef/releases/eclipse-graphical-editing-framework-gef-gef-classic-3.20.0

BR,
Alois


> 
> Note that the list of projects reflects our long time practice of
> only including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that
> projects that have been "sponsored in" by participating projects are
> absent from the list. This is per the requirements. I expect that
> these requirements will change in some future release.
> 
> A lot of the releases are quite old, and based on the activity in the
> simrel.build repository,  at least a few projects need to create some
> release records, and some may need to engage in a progress review
> (I've done my usual thing of making by best guess based on the
> release records in the system).
> 
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record, and let me
> know. If your project has not engaged in a progress (or release)
> review in more than one year, please engage with the EMO ASAP to
> schedule a review.
> 
> Be sure to set the New and Noteworthy URL in your release record: it
> is through this relationship that we build the aggregate N
> 
> Please make sure that you've made your best effort to engage in the
> IP Due Diligence Process for all third party content before you
> engage with the EMO for review. Bear in mind that you should be
> engaging in the IP Due Diligence Process on an ongoing basis and that
> all releases (regardless of whether or not they correspond with a
> progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash
> License Tool and the ability to use it to automatically create review
> requests, it should be easier than ever before to engage (the README
> has extensive information on how to engage, and does include some
> pointers for using it with Eclipse Tycho-based builds). Connect with
> the EMO if you need assistance.
> 
> Here are some things that I've observed:
> 
> Eclipse Client Platform has been removed.
> 
> The aggrcon files for the following projects are disabled; if any of
> these projects are dropping from the release, please let me know:
>  * Eclipse Xpand
>  * Eclipse BPMN2 Modeler Project
>  * Eclipse RCPTT
> Let me know what I've missed.
> 
> Thanks,
> 
> Wayne
> -- 
> Wayne Beaton
> Director of Open Source Projects | Eclipse Foundation
> 
> My working day may not be your working day! Please don’t feel obliged
> to read or reply to this e-mail outside of your normal working hours.
> ___
> 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] Eclipse IDE 2024-06 Project Participation Page

2024-05-23 Thread Mickael Istria via cross-project-issues-dev
Hi Wayne, all,

LSP4E will contribute 0.26.1 (unless we have to create another release)
https://projects.eclipse.org/projects/technology.lsp4e/releases/0.26.1
Wild Web Developer will contribute 1.3.5
https://projects.eclipse.org/projects/tools.wildwebdeveloper/releases/1.3.5

Cheers,
___
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] Eclipse IDE 2024-06 Project Participation Page

2024-05-22 Thread Christian Dietrich via cross-project-issues-dev
Mwe is 2.18.0 and Xtext is 2.35.0

Wayne Beaton via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> schrieb am Mi. 22. Mai 2024 um 23:56:

> Greetings folks!
>
> I've assembled the release information for participating projects here
> .
>
> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build 
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> , and
> let me know. If your project has not engaged in a progress (or release)
> review  in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
>  on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool  and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> -based builds).
> Connect with the EMO if you need assistance.
>
> Here are some things that I've observed:
>
> Eclipse Client Platform has been removed.
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> 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] Eclipse IDE 2024-06 Project Participation Page

2024-05-22 Thread Jonah Graham via cross-project-issues-dev
Hi Wayne,

CDT has two components for the release, the normal CDT quarterly release
https://projects.eclipse.org/projects/tools.cdt/releases/11.6.0 and the
first CDT LSP based plug-ins that supplement CDT are being contributed to
SimRel for this release in
https://projects.eclipse.org/projects/tools.cdt/releases/2.0.0-cdt-lsp

In the future we may combine the CDT LSP component release into the main
CDT release, but for now we expect it may have a different cadence and it
is built independently.

Thanks
Jonah

~~~
Jonah Graham (he/him)
Kichwa Coders
www.kichwacoders.com


On Wed, 22 May 2024 at 17:56, Wayne Beaton via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> wrote:

> Greetings folks!
>
> I've assembled the release information for participating projects here
> .
>
> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build 
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> , and
> let me know. If your project has not engaged in a progress (or release)
> review  in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
>  on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool  and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> -based builds).
> Connect with the EMO if you need assistance.
>
> Here are some things that I've observed:
>
> Eclipse Client Platform has been removed.
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> 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] Eclipse IDE 2024-06 Project Participation Page

2024-05-22 Thread Jeff Johnston via cross-project-issues-dev
Hi Wayne,

Linux Tools was missing project release records.  I have updated and added
one for 8.15.0 which is the release for 2024-06.

Thanks,

-- Jeff J.

On Wed, May 22, 2024 at 5:56 PM Wayne Beaton via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> wrote:

> Greetings folks!
>
> I've assembled the release information for participating projects here
> .
>
> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build 
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> , and
> let me know. If your project has not engaged in a progress (or release)
> review  in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
>  on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool  and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> -based builds).
> Connect with the EMO if you need assistance.
>
> Here are some things that I've observed:
>
> Eclipse Client Platform has been removed.
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> 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] Eclipse IDE 2024-06 Project Participation Page

2024-05-22 Thread Matthias Sohn via cross-project-issues-dev
On Wed, May 22, 2024 at 11:56 PM Wayne Beaton via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> wrote:

> Greetings folks!
>
> I've assembled the release information for participating projects here
> .
>

JGit and EGit will contribute 6.10.0 to 2024-06


> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build 
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> , and
> let me know. If your project has not engaged in a progress (or release)
> review  in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
>  on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool  and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> -based builds).
> Connect with the EMO if you need assistance.
>
> Here are some things that I've observed:
>
> Eclipse Client Platform has been removed.
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
> Thanks,
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> 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


[cross-project-issues-dev] Eclipse IDE 2024-06 Project Participation Page

2024-05-22 Thread Wayne Beaton via cross-project-issues-dev
Greetings folks!

I've assembled the release information for participating projects here
.

Note that the list of projects reflects our long time practice of only
including projects whose teams are actively participating in the
simultaneous release. If you look hard enough, you'll notice that projects
that have been "sponsored in" by participating projects are absent from the
list. This is per the requirements. I expect that these requirements will
change in some future release.

A lot of the releases are quite old, and based on the activity in the
simrel.build  repository,
at least a few projects need to create some release records, and some may
need to engage in a progress review (I've done my usual thing of making by
best guess based on the release records in the system).

If your project is contributing a different release than what you see here,
please ensure that you've created a release record
, and let
me know. If your project has not engaged in a progress (or release) review
 in more than
one year, please engage with the EMO ASAP to schedule a review.

Be sure to set the New and Noteworthy URL in your release record: it is
through this relationship that we build the aggregate N

Please make sure that you've made your best effort to engage in the IP Due
Diligence Process for all third party content before you engage with the
EMO for review. Bear in mind that you should be engaging in the IP Due
Diligence Process
 on an ongoing
basis and that all releases (regardless of whether or not they correspond
with a progress or release review) must only contain content that has been
vetted through the due diligence process. With the Eclipse Dash License Tool
 and the ability to use it to
automatically create review requests, it should be *easier than ever*
before to engage (the README has extensive information on how to engage,
and does include some pointers for using it with Eclipse Tycho
-based builds).
Connect with the EMO if you need assistance.

Here are some things that I've observed:

Eclipse Client Platform has been removed.

The aggrcon files for the following projects are disabled; if any of these
projects are dropping from the release, please let me know:

   - Eclipse Xpand
   - Eclipse BPMN2 Modeler Project
   - Eclipse RCPTT

Let me know what I've missed.

Thanks,

Wayne
-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation


My working day may not be your working day! Please don’t feel obliged to
read or reply to this e-mail outside of your normal working hours.
___
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