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

CRW 2.1 Overall Epic

    XMLWordPrintable

Details

    • CRW 2.1 Overall Epic
    • RHDP-232 - 1. Maintain existing portfolio commitments
    • 100
    • 100% 100%

    Description

      CRW 2.1.0

      AirGap Support

      LANGUAGES TEAM

      DOC TEAM

      Use RHEL based Images PROD TEAM / IDE2 TEAM / Florent

      Complete list of server, runtime, & sidecar containers involved in CRW 2 productization

      • add missing sync jobs for internals containers (pluginbrokers, machineexec, etc.)
      • Devfile registry airgap version (projects included) - not working – would need to precache these projects zips in a tarball and expand them in Brew build

      Other 2.1.0 related issues

      • Git+SSH improvements IDE1 TEAM

      QE

      Attachments

        Issue Links

          clones

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CRW-313 CRW 2.0 Overall Epic / Do All The Things!

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          incorporates

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CRW-565 CRW 2.1 - Create / improve syncs between up and downstream projects

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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CRW-289 Stack with JWS 3.1, Tomcat, openjdk11, Red Hat AMQP

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          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

          Feature Request - Feature requests from customers and/or users CRW-544 CRW 2.1 plugins+images

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is cloned by

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

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is documented by

          Sub-task - The sub-task of the issue RHDEVDOCS-1077 Document workspace use in restricted env

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

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-1581 Document the various places where Che can be configured

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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RHDEVDOCS-1582 Fix and unify language of in-app messages

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

          Activity

            People

              pdave@redhat.com Parag Dave
              mbenitez@redhat.com Martha Benitez
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: