On 21 Nov 2014, at 20:22, Fred Bricon <fbricon(a)gmail.com&gt; wrote: I believe that impacts us, wdyt? ---------- Forwarded message ---------- From: Greg Watson <g.watson(a)computer.org&gt; Date: Fri, Nov 21, 2014 at 11:24 AM Subject: [cross-project-issues-dev] TM withdrawal from Mars To: Cross project issues <cross-project-issues-dev(a)eclipse.org&gt; The Target Management (TM) project is comprised of two main projects: Remote System Explorer (RSE) and Terminal. Only the Terminal project is under active development, and there are plans currently to merge this with the TCF Terminal project. We are planning to have one final release of TM (3.7) to coincide with Luna SR2, and then only provide service releases on an as-needed basis. As a consequence, we don’t have the resources to contribute to a Mars release, so are notifying everyone of our intention to withdraw from Mars. Please let us know if there are any comments or concerns regarding this. Regards, Greg _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev(a)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 -- "Have you tried turning it off and on again" - The IT Crowd _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

So it is going to be only RSE after Terminal is merged into TCF Terminal project.

Do you know if it is really time consuming to just maintain RSE part to make it into Mars release?

Denis On 11/21/2014 11:38 AM, Max Rydahl Andersen wrote: > That would be rather disastrous if that removes the support for Ftp > and ssh access that is used in our remote deployment :/ > > /max > http://about.me/maxandersen > > > On 21 Nov 2014, at 20:22, Fred Bricon <fbricon(a)gmail.com > <mailto:fbricon@gmail.com>> wrote: > >> I believe that impacts us, wdyt? >> >> ---------- Forwarded message ---------- >> From: *Greg Watson* <g.watson(a)computer.org >> <mailto:g.watson@computer.org>> >> Date: Fri, Nov 21, 2014 at 11:24 AM >> Subject: [cross-project-issues-dev] TM withdrawal from Mars >> To: Cross project issues <cross-project-issues-dev(a)eclipse.org >> <mailto:cross-project-issues-dev@eclipse.org>> >> >> >> The Target Management (TM) project is comprised of two main >> projects: Remote System Explorer (RSE) and Terminal. Only the >> Terminal project is under active development, and there are plans >> currently to merge this with the TCF Terminal project. We are >> planning to have one final release of TM (3.7) to coincide with Luna >> SR2, and then only provide service releases on an as-needed basis. >> As a consequence, we don’t have the resources to contribute to a >> Mars release, so are notifying everyone of our intention to withdraw >> from Mars. >> >> Please let us know if there are any comments or concerns regarding >> this. >> >> Regards, >> Greg >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev(a)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 >> >> >> >> -- >> "Have you tried turning it off and on again" - The IT Crowd >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> <mailto:jbosstools-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On 24 Nov 2014, at 09:03, Mickael Istria <mistria(a)redhat.com&gt; wrote: I'm not sure this is *so* critical. There message means that TM won't be in Mars by default, and that they don't plan new development on the project. The removal of TM from Mars doesn't prevent us from consuming it in our TP. We actually don't even use the Mars repo to get TM currently, but already their dedicated repo. The fact that there won't be new development is not important as long as they welcome patches. So the project is not "killed" in a way that it's not usable any more, it's only that not much will happen from its current contributors. -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On 11/24/2014 09:16 AM, Max Rydahl Andersen wrote: > If it is not available in Mars we can't really depend on it without > we start bundling it and then we own the maintaence of It risking > others will bundle other versions and we'll be incompatible. It is > bad enough there now are multiple terminals, but multiple ways to > define and connect to remote hosts for file transferring. That would > be a mess. Why not simply contributing to the project in case we have things to contribute?

I don't understand why being in Mars/not being in Mars makes a difference about how to contribute to this project and how much we can rely on it.

It's just that current contibutors are resigning from this project, it doesn't require anyone to fork it.

> So sure, there are hacks for bundling this in. None of them are > sustainable if the project is looking for termination. If we don't want project to terminate, and if multiple people need it, then it's up to its adopters (including us) to affirm that we are ready to make the necessary efforts to provide and review patches to keep the project somehow alive. Given the maturity of the project, it shouldn't represent too much work to keep it alive. Things will be a mess only if we let them be a mess, but just not changing anything to current state of the project would be enough to avoid that mess.

However, if there is a better replacement, it may be a good time to use the better one; but if there is not, then we should IMO step up and say that we don't want project to terminate.

> why are we using their dedicated repo and not the release train as we > do for other things ? To get source for Dev to or? Yes, I think so, on Rob's request.