TM Future Planning

Collect input for the planning process for next year's DSDP Target Management Release (Eclipse Ganymede train, tentatively TM 3.0, June 2008) as well as the upcoming service releases (DSDP-TM 2.0.x). Goals of this page are

Collect ideas and Requirements for Target Management Ganymede and beyond

Find out who needs what features

Find out who would be willing to work on what

This is a collaborative Wiki, so everyone in the community is welcome to contribute to the discussion by simply modifying the page. Please sign up by declaring your interest or willingess to contribute on the individual items below. Our Themes and Priorities need to be aligned with the global and DSDP Requirements.
As soon as a feature description is sufficiently clear and there is some group supporting a feature, Bugzilla entries should be used for tracking requests. When finalizing the plan, bugzilla plan items will be created for grouping related work items together in order to track them.

Should it be TM 2.1 or TM 3.0?

Themes "scaling down" and "be a better framework" strongly encourage heading for TM 3.0 such that we are not burdoned by a promise to maintain old APIs

Doing 2.1 might be possible but harder than going for 3.0 right away; Finishing the UI/Non-UI refactoring is essential to complete for the next release

As it stands now, we see no clear requirement to be backward compatible with next year's release. If community wants it please speak up on the newsgroup or mailing list. We think we'll better be going for TM 3.0 since not entirely happy with APIs yet. Though we'd strive to keep API changes small.

Priorities

We have not yet agreed on clear priorities, but naturally those themes will be carried on first that have most interested parties, and where those interested parties actually contribute code, patches or committers.

In the list of themes below, typically those themes or work items that we feel to be more important appear first. Not all items of a theme may be addressed, especially those appearing further down in the list for a theme would typically receive less attention.

Community members can influence the planning process by declaring their interest, and/or especially declaring their willingness to contribute work on the themes.

Contribute: items below do not yet indicate a committment to actually contribute but do declare willingess of the signed up parties.