Skip to main content
Jump to: navigation, search

TCF/DraftPlan15

< TCF

TCF 1.5 DRAFT plan

TCF 1.5 is planned to release on June 28, 2017.
See the 1.5 New and Noteworthy and the TCF 1.5 Release Review.

See also previous TCF/DraftPlan14, TCF/NewIn14 | project management: TCF on the Eclipse PMI | Upcoming TCF/DraftPlan16


Compatibility

TCF 1.5 is planned to release with Oxygen/Simultaneous_Release_Plan on June 28, 2017. An earlier release is possible if requested by the communities; then Eclipse Oxygen would come with TCF 1.6.

At any rate, we will keep API's compatible:

  • TCF protocol must remain 100% compatible with TCF 1.4 (it's part of the TCF value proposition)
  • TCF Java API must remain 100% binary compatible with TCF 1.4 (we have clients coding against it)
  • TCF Python and C API should remain 100% compatible (we have clients but this is source compatibility so they can rebuild or use version checks)
  • All API Additions must be tagged with @since 1.5 comments.

Operating Environments

  • Java 7 is planned to remain the Bundle-RequiredExecutionEnvironment for Java code (since we plan to remain compatible down to Eclipse 4.4 Luna as per below, and Luna used Java 7).
  • We want to continue being compatible with Eclipse 4.4 Luna, since Luna is the last Eclipse release supported on CentOS 5 hosts and is still used in some organizations.
    • New features may depend on newer Eclipse Platform or CDT Capabilities; in such cases, those features will be coded in a way that the rest of TCF can still run on Luna, but the new capability will obviously only be available on the newer Eclipse.
  • Support for older Eclipse Platform (Kepler, 3.8.2) will continue on a "best effort" basis but will not be committed.
  • To be discussed:
    • Do we need any test job using Java 8 ? - Linuxtools project has reported that Jobs with Java 8 run faster.
    • Do we still need a test job against Eclipse 3.8.2 + CDT 8.3 ? - Note that CDT 8.4 only supports Eclipse 4.x

Obsoleted / Deprecated Functionality

  • None currently planned.

Proposed Themes

As with the past releases, outstanding quality and robustness is the primary concern of the TCF project. This shall be supported through continued investment in the DWARF reader, architecture coverage and test automation.

Beyond that, the themes below only list current priorities that we want to focus on.

Improve Getting Started and API Documentation

Interested Parties: Wind River

  • We want to make it easier for 3rd parties to understand, and code against the TCF API's.
    • API Docs shall be brought back in sync with the Code
      • Tools shall be investigated for auto-generating more of the docs (potentially based on the Python bindings)
    • This shall be supported by providing simple examples for commonly needed functionality.
    • We also want to provide Tutorials / Videos that showcase the TCF / Target Explorer functionality as available from Eclipse.

Improve Arm64 Debug Support

Interested Parties: Wind River

  • Improve the Arm64 stack crawler to support VxWorks compilation

Provide a TCF Communication Channel through WebSockets

Interested Parties: Wind River

Make the The TCF Python Binding more complete

Interested Parties: Wind River

  • We want to add TCF APIs to the Python binding, which are currently only available in the Java and C bindings
    • DPrintf Service, also related to docs as per above

Back to the top