Bug 225105 - [tcf][planning] Come up with a Roadmap for TCF
Summary: [tcf][planning] Come up with a Roadmap for TCF
Status: ASSIGNED
Alias: None
Product: TCF
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 270607
  Show dependency tree
 
Reported: 2008-04-01 10:17 EDT by Martin Oberhuber CLA
Modified: 2011-04-28 00:14 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2008-04-01 10:17:05 EDT
The TCF component is currently incubating and therefore separated from the Ganymede Release train as well as the TM/RSE release train.

We need to come up with a roadmap and dates for TCF:

* When do we want to provide milestone releases for public consumption?
  - What other versions will TCF depend on (Eclipse 3.4, TM 3.0, DSF 1.0)?
* What are the major goals that we want to achieve before going 1.0?
  - Is there a lot of yet unknown stuff where we'll need public review?
  - Do we want any 0.x releases before going 1.0? When?
* When do we want to go 1.0?
  - With Eclipse 3.5 June 2008 or any time earlier? Or probably later?
  - Do we even know this yet?

Remaining in Incubation (0.x releases) has some advantages, i.e. we don't need to think so much about API backward compatibility; we can leverage the Parallel IP Process if we want, to speed up inbound licensing of 3rd party libs; but on the other hand, going 1.0 might further increase community growth and public adoption.

I'd personally suggest going 1.0 with Eclipse 3.5 in June 2008, and planning one or two 0.x releases for public consumption between (e.g. one with Eclipse 3.4 in June 2008, and another one late October 2008). That's purely what I think would be good from a Community point of view, since I'm not yet aware of the detailed technical plans.

Whatever we decide, some decision would be good since Community likes to get an idea what's ahead and when it's ahead.

Discussion is opened.