I did say “planning”. ;). As projects run out of committers, we need to make sure everyone is aware of the situation and so they can consider how it affects them.
Doug. From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Wayne Beaton Sent: Monday, December 18, 2017 2:32 PM To: Cross project issues <cross-project-issues-dev@eclipse.org> Subject: Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? No. We'll start that process in January in preparation for the M5 build. Besides, removing it breaks Web Tools (at least). I'm pretty sure that we have a volunteer to take over releng. Wayne On Dec 18, 2017 9:48 AM, "Doug Schaefer" <dschae...@blackberry.com<mailto:dschae...@blackberry.com>> wrote: We should probably start planning on the removal of DTP now. It’s not clear it has the resources to even do builds going forward. Doug. From: cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org> [mailto:cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org>] On Behalf Of Daniel Megert Sent: Monday, December 18, 2017 4:48 AM To: Cross project issues <cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>> Subject: Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? It's good enough to just do a build. The API was deprecated for ten years already. After removing it for Oxygen (4.7) a simple build would have failed with a compile error. Dani From: "Torkild U. Resheim" <torki...@gmail.com<mailto:torki...@gmail.com>> To: Cross project issues <cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>> Date: 16.12.2017 21:11 Subject: Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin? Sent by: cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org> ________________________________ Yes, I think that’s a good idea Stephan. One could possibly set up the build to fail when using deprecated API, in order to get an early warning. I’m not aware of a way of making Tycho do so though. I guess having a no-warnings policy and set the compiler up to fail on warnings is an option. Best regards, Torkild > 16. des. 2017 kl. 17:54 skrev Stephan Herrmann > <stephan.herrm...@berlin.de<mailto:stephan.herrm...@berlin.de>>: > > Another option could be: even "inactive" projects could be required, > to perform builds against each SimRel milestone, even when contributing > a previous version. This should ensure that code still works (compiles > and passes tests) against updated dependencies. > > I don't think this should be much of a burden on "maintainers". > > Stephan [attachment "signature.asc" deleted by Daniel Megert/Zurich/IBM] _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org> 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 cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org> 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 cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
