> Eclipse PDT's aggrcon is disabled > Eclipse DLTK's aggrcon is disabled.
AFAICT these are not disabled. They have features within them disabled related to Mylyn though. I initially only disabled Mylyn <https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/189614> in the hope someone may enable them again soon. DLTK does look inconsistent. What is contributed is a 6.2m3 p2 URL, but the current release is 6.1 in PMI. I leave the discussion on termination/etc to the Technology PMC as Alex had suggested. If DLTK goes, I think PDT does too as PDT depends on DLTK. Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Tue, 30 Aug 2022 at 23:27, Wayne Beaton < wayne.bea...@eclipse-foundation.org> wrote: > Greetings folks! > > I've assembled my first pass at the Eclipse IDE 2022-09 participation page > <https://projects.eclipse.org/releases/2022-09>. > > Please have a look to ensure that I've captured the release version of > your project correctly. If you're contributing a new release, please be > sure to create the release record. > > You may notice that Maven Integration for Web Tools Platform is dropped > from the project list. That project was terminated and its resources were > merged into Maven Integration. > > Some anomalies that I've noticed: > > - The Eclipse Platform release record has not been created yet; > - Eclipse ACTF's aggrcon is disabled; > - Eclipse PDT's aggrcon is disabled; and > - Eclipse DLTK's aggrcon is disabled. > > Can a committer from Eclipse Platform please create the release record? > > Regarding the disabled contributions... Can a representative from the > corresponding project committers please let us know if you are engaged > working on getting these contributions back into an enabled state? > > If your project is contributing a new major or minor release to 2022-09 > and you haven't engaged in a release or progress review in the year leading > up to your release date, please engage with the EMO ASAP. > > Remember that, regardless of whether or not a review is required, any > intellectual property included in any release must be fully vetted. If you > have not already done so, I recommend that you check out the Eclipse Dash > License Tool to identify any gaps in the vetting of your third-party > dependencies; look especially at the Automatic IP Team Review Requests > <https://github.com/eclipse/dash-licenses#automatic-ip-team-review-requests> > feature. > > 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
