I am purposely leaving RSE out on its own. Greg's org.eclipse.remote better suits our needs in CDT and will be going forward with that. RSE needs a new owner, or archive.
Doug. From: [email protected] [mailto:[email protected]] On Behalf Of Martin Oberhuber Sent: Tuesday, December 19, 2017 6:35 AM To: Cross project issues <[email protected]> Subject: Re: [cross-project-issues-dev] Many projects have not yet opted in to participate in Eclipse Photon Regarding Target Management, IIRC there is a plan moving the Terminal to the CDT. But what about RSE? Some packages include it now (PHP, JEE, C/C++ as far as I know)... I am a TM committer, but I can not personally support TM on the release train. Martin On 15 Dec 2017, at 21:01, Wayne Beaton <[email protected]<mailto:[email protected]>> wrote: By way of background, we introduced the requirement that projects publicly state their intent to participate<https://www.eclipse.org/projects/handbook/#pmi-joining-a-simultaneous-release> in each release to ensure that everybody is actually paying attention. In the past, we've had to scramble to sort out last minute issues because (some) project teams hadn't engaged. Participation in the simultaneous release requires some ongoing investment of time and energy from those projects that join in. The deadline for stating intent to join the Eclipse Photon simultaneous release is EOB today. After that, the rules state that projects must work through their PMC to have the Eclipse Planning Council grant an exception to join after the deadline. I am pretty confident, however, that if you state your intent on this list by mid-week next week, the Planning Council will accept it. Please, get this done. Any project that has not declared an intent to participate will be removed from the aggregation build prior to the M5 release. I'll work with Fred and Mikael to deactivate builds early in the new year. AFAICT, the following projects have not stated their intention to participate. * Eclipse EGerrit * Eclipse e(fx)clipse * Eclipse Parallel Tools Platform (PTP) * Eclipse Sapphire * Eclipse Sphinx * Eclipse Target Management * Eclipse Communication Framework * Eclipse XWT * Eclipse PMF * Eclipse Orion * Eclipse Accessibility Tools Framework * Eclipse ATL * Eclipse Subversive SVN Team Provider * Eclipse Data Tools Platform If you represent one of these projects and have chosen not to participate, please let the group know. If you're listed here in error, I apologise. Please send me a harshly worded note pointing out my omission. I am working with the Eclipse Data Tools Platform, so we'll likely get that resolved shortly. The Eclipse Subversive team has indicated that they can no longer support the project, so we're going to have to sort out what (if anything) to do about that. Since I'm pretty sure that the Eclipse Packaging Project is paying attention (and I am a committer on the project), I've created a 4.8 release<https://projects.eclipse.org/projects/technology.packaging/releases/4.8> at +4 (consider this the project's declaration of participation). Thanks for your attention, Wayne -- Wayne Beaton Director of Open Source Projects The Eclipse Foundation _______________________________________________ cross-project-issues-dev mailing list [email protected]<mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
