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

[Alois Zoitl <alois.zoitl@xxxxxx>]

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&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@xxxxxxxxxxx
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev