Just FYI,
Releasing a 1.0 version of TCF is an important decision
not made easily, because
it means the intent of freezing stable APIs. We
understand the community need
for stable APIs, but on the other hand
we want to be able to react to adopters
needs with good flexibility, not bringing in a burden
of backward compatibility
too early.
We are thus considering working towards TCF 1.0, but
the decision
has not yet been officially made. The more
community feedback and
discussions we get regarding TCF APIs,
the easier it will be for us to
plan for and declare a 1.0 version!
I have added markup to the TM project plan to better
clarify its status.
Thanks,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
Pawel
Piech wrote:
Currently,
the TCF protocol, agent, and UI integration are still in pre-1.0
stage. However according to the TM project plan, bringing TCF to 1.0 release is
one of the release themes.
For my part, I would love to see the
UI-integration of TCF, which is based on DSF find its way into the CDT
project along with DSF so that we can all coordinate their development
better, and hopefully find some more contributors in the CDT community
:-)
Cheers,
Pawel