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))
(i12.03 (March 2012))
Line 35: Line 35:
 
** Opening a Specification
 
** Opening a Specification
 
** Creating a new Specification
 
** Creating a new Specification
*** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374206 Allow creating a Specification via Specification Editor]
+
*** (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'''
 
* '''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]
 
** 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
 
** Creating and deleting SpecElements
 +
*** (mj) C
 
*** Creating a new SpecHierarchy or SpecObject via SpecEditor if no elements exist yet
 
*** Creating a new SpecHierarchy or SpecObject via SpecEditor if no elements exist yet
**** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374186 Allow creating SpecElements in Specification Editor if editor is empty (No SpecElements 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 (SpecHierarchy)
 
*** Crating a new child via context menu (SpecObject)
 
*** Crating a new child via context menu (SpecObject)
Line 46: Line 49:
 
*** Creating a new sibling via context menu (SpecObject)
 
*** Creating a new sibling via context menu (SpecObject)
 
*** Deleting SpecElements
 
*** 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=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]
 
**** 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
 
** 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 SpecHierarchy(s) via context menu
 
*** Cut and Paste SpecObject(s) via content menu
 
*** Cut and Paste SpecObject(s) via content menu
Line 62: Line 68:
 
*** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374203 Drag and Drop of multiple Spec Elements does not work]
 
*** 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 (Shift SpecElement)
 
*** Drag and Drop SpecElements (Shift SpecElement)
*** Drag and Drop SpecElements with hold CRTL key (Copy SpecElement)
+
*** Copy Drag and Drop SpecElements
*** Drag and Drop SpecElements with hold ALT key (Create Link)
+
*** 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
 
** Changing properties in properties view
 
*** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=368254 Sort PropertyView]
 
*** Bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=368254 Sort PropertyView]
Line 110: Line 118:
 
** Reduce Context Menus to minimum
 
** Reduce Context Menus to minimum
 
** Migrate and update documentation
 
** 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]
 
* [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]

Revision as of 11:18, 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.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.