Skip to main content
Jump to: navigation, search

Difference between revisions of "RMF/Roadmap"

< RMF
(i12.03 (March 2012))
(i12.03 (March 2012))
Line 9: Line 9:
 
== i12.03 (March 2012) ==
 
== i12.03 (March 2012) ==
  
Goals for this release are:
+
The objective of this iteration is to improve usability.  The following list will help us identify our priorities for this iteration.
 +
 
 +
If you want to help, please stick to the following guidelines:
 +
* Each bullet represents a mini-usecase (is there a better word?).  It should be pretty clear what is meant.
 +
* Each bullet has a status.  The quality is rated A = good to D = insufficient.  If you rate, please add your initials, so that we can track down people.
 +
* Please update the status as you see fit.
 +
* Please add mini-usecases, but don't remove any (unless they are obviously duplicates)
 +
* If you find an issue with a mini-usecase that is actually a bug, please file it in bugzilla and add a link to that bug.
  
 
Use cases:
 
Use cases:
Line 15: Line 22:
 
* '''Creating a ReqIF model file'''
 
* '''Creating a ReqIF model file'''
 
** Improve the wizard (i.e. use IF attribute names, if permitted)
 
** Improve the wizard (i.e. use IF attribute names, if permitted)
 +
*** (mj) Status: C
 +
*** (mj) It would be nice if the wizard would already allow some customization.
 +
*** (mj) If the ProR perspective is selected, the wizard should be accessible directly under the "New" menu.
 
** Help people looking for a "ProR Project"
 
** Help people looking for a "ProR Project"
 +
*** (mj) Status: D
 +
*** (mj) Users were looking for a "ProR Project", but there is no such project type.  We should catch somehow those users (e.g. by using a dummy-project-type)
 
* '''ReqIF Main Editor'''
 
* '''ReqIF Main Editor'''
 
** Changing the title of the ReqIF model
 
** Changing the title of the ReqIF model

Revision as of 10:11, 16 March 2012

General Considerations

  • We want to graduate from incubation by the end of 2012
  • We use Git Flow for now, but will switch to a new process before graduating from incubation, to support multiple release branches (Eike)
  • CDO has tooling for API evolution, we should look into employing it before graduating.

Upcoming Integration Builds

i12.03 (March 2012)

The objective of this iteration is to improve usability. The following list will help us identify our priorities for this iteration.

If you want to help, please stick to the following guidelines:

  • Each bullet represents a mini-usecase (is there a better word?). It should be pretty clear what is meant.
  • Each bullet has a status. The quality is rated A = good to D = insufficient. If you rate, please add your initials, so that we can track down people.
  • Please update the status as you see fit.
  • Please add mini-usecases, but don't remove any (unless they are obviously duplicates)
  • If you find an issue with a mini-usecase that is actually a bug, please file it in bugzilla and add a link to that bug.

Use cases:

Past Integration Builds

i12.01 (January 20th, 2012)

pror.org core-9.0.0 (October 8th 2011)

core-9.0.0 was the last release before the code base was migrated to the Eclipse Foundation.

Back to the top