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

Mylyn/UCOSP 2015 Plan

< Mylyn
Revision as of 16:55, 9 September 2015 by Sam.davis.planview.com (Talk | contribs) (Created page with "The following is a rough implementation plan corresponding to Mylyn/UCOSP_2015_Project. No doubt many details still need to be worked out during the implementation, and mo...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The following is a rough implementation plan corresponding to Mylyn/UCOSP_2015_Project. No doubt many details still need to be worked out during the implementation, and more stories may be needed. For each top-level list item (story), when starting work, a bug should be created as a child of bug 476925 with severity "enhancement" and [UCOSP] in the summary; the sub-list items are acceptance criteria.

Stories (in Priority Order)

1)

  • parse build status from comments and add to task data
  • show build status in patch set section
  • hide build notifications from comment stream

2)

  • parse review descriptions to create a mapping from tasks to reviews
    • update mapping when reviews are synchronized
    • persist mapping using an XML or JSON file for each task
    • load mapping at startup
    • do not allow reviews to be mapped to other reviews
  • create an API for a connector to provide a summary of incoming changes and implement in the Gerrit connector or reviews framework
  • contribute reviews section to task editor showing associated reviews
    • contribute section only if task has associated reviews
    • display summary of incoming changes for each review in reviews section
    • display CR and V columns like the Gerrit dashboard view
    • add task list tooltip to reviews section

3)

  • create incoming_review state for tasks, with same guaranteed visibility rules as incoming
  • set incoming_review state on tasks based on incoming state of associated reviews
    • set incoming_review state on associated task when a review gets an incoming
    • clear incoming_review state on associated task when no associated review is incoming
  • create glasses decorator for incoming_review state
  • add glasses decorator to UI legend

4)

  • Add a setting to the Gerrit repository settings to select the default workflow for that repository
    • Setting is called: "How do you use Gerrit?" and has 2 options, "With an issue tracker" and "By itself"
    • Each option includes a short explanation
    • do not allow finishing settings page without selecting an option
    • if no option is selected (for existing repositories) default to old behaviour
  • when reviews are synrchonized, mark them as artifacts if they are not tasks
    • if the review has an associated task and has no context, scheduled date, or due date, set a property on its ITask if the "issue tracker" workflow is selected for the Gerrit repository
  • add task list filter for review artifacts
    • do not provide any UI for disabling the filter because this is controlled on a per-repository basis
  • remove task affordances from the review artifact editor
    • when opening a review that is marked as an artifact, suppress the task context and scheduling affordances, and 3rd party contributed task editor sections
  • display mess for existing users on upgrade prompting them to choose one workflow for all existing Gerrit repositories
    • on startup, if 1 or more Gerrit repositories have no workflow specified, display notification using task list message service
    • clicking notification opens dialog explaining workflows
    • selected workflow is applied to all existing Gerrit repositories
    • existing reviews are *not* changed

5)

  • Provide an affordance for converting between review artifacts and review tasks

Additional Stories

  • show code review votes in patch set section
  • show summary of approvals in patch set headers
  • prevent activating review artifacts (e.g. using task list filter or ctrl+F9)
  • add Mylyn Builds integration to review editor
    • create a BuildToolbar in mylyn.builds and use it in the patch set section if mylyn.builds is installed
      • if build repository doesn't exist, buttons should open add repository dialog
    • display "Connect build repository..." link in place of the toolbar if builds is not installed,
      • link should open an information dialog explaining how to install Mylyn Builds with a checkbox to hide the link

Back to the top