Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
Minor release with Eclipse Neon. Focus on quality, robustness, Ada support and ARM stack crawling.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
TCF connections use a plaintext protocol based on JSON by default, but can optionally be routed over SSL ports or tunneled through other communication channels (like SSH). This is by design, as TCF itself is focused on APIs and communication, independent of a secure (or not so secure) channel.
A TCF server that runs with root privileges will provide root access to the target by default. Using a firewall is therefore recommendet to protect access to the TCF server ports.
A growing number of adopters reports success building a debugger based on TCF. While the existing "Getting Started", "Porting Guide" and "API Docs" are good, there is also continued demand on more documentation and examples.
Commercial adopters confirm excellent usability of the TCF software. For plain Open Source users, some requests on the mailing list indicate confusion around end-to-end workflows. This will be addressed with more user-facing documentation (Tutorials, videos).
No EOL functionality this year.
There are plans to stop supporting Eclipse Platform 3.x in the upcoming TCF 1.5 release.
Main interest of adopters is building their own debuggers using TCF building blocks, as well as getting commercial grade Eclipse integration for existing debuggers. In this respect, the well-designed TCF APIs are a very strong asset, along with the TCF C building blocks (agent) being released under the permissive EDL (BSD) license.