Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

this point what the plan is. >> >> >> >> 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 &g

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

works on. >> >> >> >> We really need to be crystal clear at this point what the plan is. >> >> >> >> Doug. >> >> >> >> *From:* cross-project-issues-dev-boun...@eclipse.org [mailto: >> cross-project-issues-dev-boun...@eclipse.o

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

> <mailto:cross-project-issues-dev-boun...@eclipse.org>] On Behalf Of Nick Boldt > Sent: Monday, February 12, 2018 9:49 AM > To: issues, Cross project <cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org>> > Subject: Re: [cros

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

dev@eclipse.org> Cc: Kaloyan Raev <kaloya...@zend.com> Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled Strictkly speaking, the "leadership chain" can decide to add or remove committers if the project is determined to be dysfunctional. The leadership

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

what the plan is. > > > > Doug. > > > > *From:* cross-project-issues-dev-boun...@eclipse.org [mailto: > cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Nick Boldt > *Sent:* Monday, February 12, 2018 9:49 AM > *To:* issues, Cross project <cross-project

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

, Cross project <cross-project-issues-dev@eclipse.org> Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled AFAIK it's out. But if I find time to submit the changes from my/Rob's github fork as gerrit review(s) back to the master fork on git.eclipse.or

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

AFAIK it's out. But if I find time to submit the changes from my/Rob's github fork as gerrit review(s) back to the master fork on git.eclipse.org, that team can evaluate it, merge it, and maybe decide they want to be included for M6. Then it'll be up to the Planning Council to approve the late

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

ent:* January 31, 2018 5:33 PM > *To:* cross-project-issues-dev@eclipse.org > *Reply-to:* cross-project-issues-dev@eclipse.org > *Subject:* Re: [cross-project-issues-dev] SimRel - TM contribution has > been disabled > > > > On Wed, Jan 31, 2018 at 11:14 PM, Doug Schaefer <

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

-issues-dev@eclipse.org Reply-to: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled On Wed, Jan 31, 2018 at 11:14 PM, Doug Schaefer <dschae...@blackberry.com<mailto:dschae...@blackberry.com>> wrote: Does

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

On Wed, Jan 31, 2018 at 11:14 PM, Doug Schaefer wrote: > Does anyone want these contributions to keep RSE alive? > I don't think the opinion of others should be used as a criterion here. The thing is that if Nick, Rob or whoever have authored good patches, it's still

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

OK, but what happens if the project is dead, no longer being developed, and was kicked off the simrel train for its inactivity / failure to declare intent on time? I'll happily contribute the fixes, but if no one reviews them or if they're bigger than the 1000 LOC limit, we're going to have a bad

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

On Wed, Jan 31, 2018 at 6:01 PM, Nick Boldt wrote: > Should we want to re-include RSE in Photon, we could do so for M6 if > someone grants me a place to publish it & permission to do so. We've got a > fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and >

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

Hi, TCF is re-enabled after removing TCF/RSE integration from SimRel. Thanks, Eugene -Original Message- From: Frederic Gurr [mailto:frederic.g...@eclipse-foundation.org] Sent: Tuesday, January 30, 2018 1:13 PM To: Cross project issues Cc: Eugene

Re: [cross-project-issues-dev] SimRel - TM contribution has been disabled

Should we want to re-include RSE in Photon, we could do so for M6 if someone grants me a place to publish it & permission to do so. We've got a fork [1] that updates the old Oxygen-based TM/RSE build to Tycho 1.0, and it currently builds against Photon.0.M4. This could easily be moved to an

[cross-project-issues-dev] SimRel - TM contribution has been disabled

Hi, As announced before, the Target Management (TM) contribution has been disabled. Even though some code has been moved to CDT (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=527575), there are still two features remaining (org.eclipse.rse and org.eclipse.rse.useractions). Since disabling