Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] [tm-dev] TM Terminal and CDT plans
Note that in parallel with this discussion, we've realized that the RSE stuff might have to go on for a while longer as JBoss Tools still depends on it for its server adapter stuff. I'm told that org.eclipse.remote isn't feature-rich enough to use instead... but this is likely based on the state of things from 2018 when last I tried to convince people to dump RSE (dead project) and move to o.e.remote (active project). Not trying to impugn your work, just passing on what I've been told. 

What would you say to the idea of moving some/all of RSE into CDT just to keep it alive? You might not have to do anything to detangle the circular deps at that point, if it comes along for the ride. :)

Nick



On Thu, Jan 23, 2020 at 3:26 PM Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Thanks Nick for the offer - I will refer to your scrips as needed. I have also done recent merges for various CDT repos which is what kicked off this discussion again.

I have raised Bug 559474 and sent notice to tools-pmc and emo about this for their approvals and to address any process issues.

Thanks,
Jonah




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 20:12, Nick Boldt <nboldt@xxxxxxxxxx> wrote:
+1. If you need assistance with the "move a project to another repo and preserve history" technique, I've done that a few times (for the various DTP, TM, WTP projects we moved/merged a couple years ago). If it's useful, here are some gist scripts:


Before you can complete the copy/merge into the destination repo, you need to get these steps done:

1. disable IP check (web master)
2. forge author (should be already on by default)
3. grant forge committer (web master)
4. grant forge server (web master)

And according to Wayne back in 2018, "Merging repositories that both belong to the same project does not require PMC or EMO approval. Have at it."

Since CDT and TM are different projects, I suspect we need formal PMC and EMO approval. 

HTH

Nick


On Wed, Jan 22, 2020 at 11:51 AM Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Thanks Nick for merging the fix and returning the build to green.

Hello TM and CDT folk,

Based on discussions up to this point I think the plan should be:

- Move active parts of terminal code to CDT's git repo - this is everything in org.eclipse.tm.terminal namespace, except org.eclipse.tm.terminal.view.ui.rse[0] and org.eclipse.tm.terminal.connector.serial[1]
- The namespace will be preserved - i.e. no renaming of plug-ins/features
- The terminal will still be installable without any new dependencies on CDT
- The terminal will be distributed and released with CDT's releases in CDT's p2 repos (under https://download.eclipse.org/tools/cdt/)
- The terminal will continue to be contributed to simrel (just in cdt.aggrcon instead of tm.aggrcon)
- The git history of terminal will be preserved/moved to CDT
- The remaining RSE project will then be archived according to the Eclipse Project Handbook process [2] and removed from SimRel.
- All of this done in time for CDT 9.11.0 M2 / SimRel 2020-03 M2 release (aka by 3 Feb 2020)

Can I get some +1s then I can proceed with bugs and process stuff?

[0] Because of archiving RSE. This bundle/feature is not in the simrel today and it is the only bundle causing the circular dep with the rest of RSE.
[1] Because this implementation of serial is already not included in recent releases due to GPL code, See Bug 536800
[2] What happens to RSE (what will be left of Eclipse Target Management project) is somewhat independent of the rest of the list. 

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Mon, 20 Jan 2020 at 13:22, Nick Boldt <nboldt@xxxxxxxxxx> wrote:
TM and RSE re back to green.


Latest bits:


Gerrit to update to 4.5.103 from .102:


Thanks for contributing the fix to get TM/RSE back to green!

If there are any other stalled gerrits, don't hesitate to reach out to me directly on mattermost or email.

Nick


On Fri, Jan 17, 2020 at 12:59 PM Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Hello CDT and TM folks,

I have been asked to revive this merge. I believe it makes sense to bring the tm.terminal code into the CDT repo for release engineering purposes in the same way we just merged the launchbar and tools.templates into CDT.

This has been discussed on both cdt-dev and tm-dev mailing lists in the past (the thread I am replying to thread for cdt-dev and https://www.eclipse.org/lists//tm-dev/msg01214.html for tm-dev).

The current TM repo does not build (out of date target platform).

My biggest concern about doing this is the comment in the TM readme:
== Circular Dependencies

In theory, the RSE and Terminal are independent projects.

In practice, they each depend on each other, which is why we've now merged the RSE (org.eclipse.tm) and Terminal (org.eclipse.tm.terminal) repos into a single gerrit repo to resolve this cycle and make building easier.

We already have circular dependencies that we have learned to live with, but I don't really want to add RSE as a new dependency of CDT.

Before I go further down this path I want to solicit input. Does anyone know why this stalled last time? Should we just fix the TM builds as they are (gerrit)?

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Thu, 25 Jan 2018 at 11:26, Jeff Johnston <jjohnstn@xxxxxxxxxx> wrote:
A while back it was proposed that CDT bring TM Terminal to the CDT.  Doug, is there any progress on this or time-line scheduled? 

Linux Tools Docker tooling requires TM Terminal and as of Monday, Eclipse Target Management is being dropped from Photon aggregation.

-- Jeff J.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tm-dev


--

Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: CodeReady Workspaces 

IM: @nickboldt / @nboldt / http://nick.divbyzero.com



“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tm-dev
_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tm-dev


--

Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: CodeReady Workspaces 

IM: @nickboldt / @nboldt / http://nick.divbyzero.com



“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tm-dev
_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tm-dev


--

Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: CodeReady Workspaces 

IM: @nickboldt / @nboldt / http://nick.divbyzero.com



“The Only Thing That Is Constant Is Change” - Heraclitus

Back to the top