Benjamin Zeiss wrote:
We should create a rough road map. The outstanding major features that we intend to get in mid-term that i can think of right now:
- compiler integration (this includes some kind of standard way for a
compiler integration, i.e. the telelogic integration probably has to be rewritten as well. we should also investigate the openttcn integration - think they have also a compiler now rather than an interpreter - at least the openttcn guy contacted me some days ago stating that i would require visual c++ for the new version)
- metric analysis
- semantic analysis
- pattern analysis
features necessary for stability and peformance to make it actually widely usable:
- parser optimization
- incremental parser
- dependency analysis (i.e. analyze only dependant files)
maybe we should aim to have this package in the 1.0 release?
here is an idea:
0.60
- compiler integration (tau, danet. openttcn TBD)
0.70
- metric analysis
- semantic analysis
(two major features since metric analysis is basically done and only parts need to be rewritten)
0.80
- pattern analysis
0.90
- parser optimization
- incremental parser
- dependency analysis (i.e. analyze only dependant files)
1.0
- stabilizing everything from 0.90.
depending on how the pattern analysis progresses, we could swap the 0.80 and 0.90 contents. Given such a roadmap, we could indeed skip the 0.54 release and make it 0.60. All the little issues should then be spread across those versions and the 0.01 increments depending on their importance. What do you think about that?
Sounds reasonable (except that I would add "implement further refactorings" somewhere, e.g. around 0.8 and 0.9.).
If you like, I may create new release versions in JIRA, attach your feature description to each version description, and distribute the existing issues to them.
Bye, Helmut