Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-544

CRW 2.1 plugins+images

    XMLWordPrintable

Details

    • RHDP-232 - 1. Maintain existing portfolio commitments
    • 0
    • 0% 0%

    Description

      This issue is to track the list of plugins + their associated stack/sidecar images that need to be productized for CRW 2.1, then exposed from the OOTB plugin registry that will ship with CRW 2.1:

      List of plugins that are required for CRW 2.1 (approved by Stevan on 2019-12-05)

      • redhat/java11/0.50.0
      • gradle
      • quarkus
      • joaompinto/vscode-asciidoctor/2.7.7
      • redhat/rhamt/0.0.8 << SLIP TO later release, eg., 2.2
      • redhat/vscode-camelk/0.0.9
      • sonarsource/sonarlint-vscode/0.0.1

      Attachments

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CRW-507 CRW 2.1 Overall Epic

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          clones

          Feature Request - Feature requests from customers and/or users CRW-326 CRW 2.0 plugins+images

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. CRW-602 Workspace startup time is prohibitively slow

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users CRW-317 CRW 2.0 devfiles

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Feature Request - Feature requests from customers and/or users CRW-402 CRW 2.1 devfiles

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              nickboldt Nick Boldt
              mloriedo Mario Loriedo
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: