Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "RMF/Roadmap"

< RMF
(i12.03 (March 2012))
Line 4: Line 4:
 
* We use Git Flow for now, but will switch to a new process before graduating from incubation, to support multiple release branches (Eike)
 
* 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.
 
* CDO has tooling for API evolution, we should look into employing it before graduating.
 +
 +
== Use Cases ==
 +
 +
The use cases identified for RMF are documented [[RMF/Use Cases|here]].
  
 
= Upcoming Integration Builds =
 
= Upcoming Integration Builds =
Line 9: Line 13:
 
== i12.03 (March 2012) ==
 
== 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.
+
[https://bugs.eclipse.org/bugs/buglist.cgi?list_id=200551;field0-0-0=target_milestone;query_format=advanced;type0-0-0=substring;value0-0-0=12.03;product=MDT.RMF Bugzilla query of included issues]
 
+
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:
+
 
+
* '''Creating a ReqIF model file'''
+
** 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"
+
*** (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'''
+
** Changing the title of the ReqIF model
+
** Changing the comment of the ReqIF model
+
** Displaying properties of a Specification
+
** Changing properties of a Specification
+
** Opening a Specification
+
** Creating a new Specification
+
*** (mj) Status: B
+
*** (ll) Feature Request: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374206 Allow creating a Specification via Specification Editor]
+
* '''ReqIF Specification Editor'''
+
** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374189 The width of the first column in the Specification Editor is not refreshed]
+
** Creating and deleting SpecElements
+
*** (mj) C
+
*** Creating a new SpecHierarchy or SpecObject via SpecEditor if no elements exist yet
+
**** (mj) Status: D
+
**** Feature Request: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374186 Allow creating SpecElements in Specification Editor if editor is empty (No SpecElements exist yet)]
+
*** Crating a new child via context menu (SpecHierarchy)
+
*** Crating a new child via context menu (SpecObject)
+
*** Creating a new sibling via context menu (SpecHierarchy)
+
*** Creating a new sibling via context menu (SpecObject)
+
*** Deleting SpecElements
+
**** (mj) Status: D
+
**** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374181 Deleting last SpecElement in Specification Editor causes Exception]
+
**** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374183 Deleting multiple SpecElements in Specification editor via DEL key does not work]
+
** Cut and Paste
+
*** (mj) Status: D
+
*** (mj) The main problem: Cut and paste always relates to the selected element, rather than selected text (in an active editor).
+
*** Cut and Paste SpecHierarchy(s) via context menu
+
*** Cut and Paste SpecObject(s) via content menu
+
*** Cut and Paste SpecHierarchy(s) via keys
+
*** Cut and Paste SpecObject(s) via keys
+
** Copy and Paste
+
*** Copy and Paste SpecHierarchy(s) via context menu
+
*** Copy and Paste SpecObject(s) via content menu
+
*** Copy and Paste SpecHierarchy(s) keys
+
*** Copy and Paste SpecObject(s) keys
+
** Drag and Drop
+
*** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=367300 On paste / drag, we may end up with duplicate IDs.]
+
*** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374203 Drag and Drop of multiple Spec Elements does not work]
+
*** Drag and Drop SpecElements (Add as child)
+
**** Feature Request: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=375078 Drag and Drop as Child element does not work if parent has not child element yet]
+
*** Drag and Drop SpecElements (Shift SpecElement)
+
*** Copy Drag and Drop SpecElements
+
*** Link Drag and Drop SpecElements
+
**** (mj) Status: D
+
**** Main problem: the SpecRelationType has to be set by hand.  Too many clicks.
+
** Changing properties in properties view
+
*** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=368254 Sort PropertyView]
+
*** Changing properties of SpecHierarchy
+
**** Changing Object Property
+
***** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=368013 Properties View not refreshed after setting SpecObject type to null]
+
*** Changing properties of SpecObject
+
**** Changing Type Property
+
***** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=368013 Properties View not refreshed after setting SpecObject type to null]
+
** Changing properties in specification editor
+
*** Changing boolean attribute
+
**** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374213 Changing many times the value of a boolean attribute in specification editor freezes the application]
+
*** Changing enumeration attribute
+
**** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374216 Changing the value of an enumeration attribute causes a flickering of the specification editor, performance problem?]
+
*** Changing string attribute
+
**** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=367306 Dynamically adjust the row size when editing]
+
**** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=375088 Copy/Paste plain text from another source does not work in the specification editor]
+
** General Configuration
+
*** Open general configuration
+
*** Changing default label configuration
+
** Datatype Configuration
+
*** Adding a new Spec Type
+
*** Deleting a Spec Type
+
*** Adding a new attribute definition
+
*** Deleting an attribute definition
+
*** Adding a new datatype definition
+
*** Deleting a datatype definition
+
** Presentation Configuration
+
*** Adding a new presentation configuration
+
*** Deleting a presentation configuration
+
** Column Configuration
+
*** Adding a new column configuration
+
*** Deleting a column configuration
+
*** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374364 Allow reordering of columns in column configuration]
+
** Toogle SpecRelations (Links)
+
*** Show links in both directions
+
* '''Properties View'''
+
** Allow hiding of Irrelevant properties
+
* '''Other'''
+
** Support of all ReqIF features (issues with XHTML and ToolExtensions are resolved)
+
** Establish an infrastructure for Eclipse Preferences
+
** Performance
+
** Support Search
+
*** Support Replace
+
** Support filtering
+
** Copy & Paste of text in table cells
+
** Reduce Context Menus to minimum
+
** Migrate and update documentation
+
** Tips on startup
+
 
+
* [https://bugs.eclipse.org/bugs/buglist.cgi?list_id=200551;field0-0-0=target_milestone;query_format=advanced;type0-0-0=substring;value0-0-0=12.03;product=MDT.RMF Bugzilla query of included issues]
+
  
 
= Past Integration Builds =
 
= Past Integration Builds =

Revision as of 07:59, 30 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.

Use Cases

The use cases identified for RMF are documented here.

Upcoming Integration Builds

i12.03 (March 2012)

Bugzilla query of included issues

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