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

Rename CodeReady Workspaces to Red Hat OpenShift Dev Spaces (RHOSDS)

    XMLWordPrintable

Details

    • Rename CodeReady Workspaces to Red Hat OpenShift Dev Spaces (RHOSDS)
    • 50
    • False
    • False
    • To Do
    • 100
    • 100% 100%
    • Prod #215 2022-02-23

    Description

      Starting with the CRW 2.16 code base, CRW will be renamed to RHOSDS.

      This epic collects the 1000s of things we have to do to get there.

      See also https://docs.google.com/spreadsheets/d/14YNPPMHf3B6xo3eUjABO90_ybtFT56U9yLldVXIi3V8/edit#gid=0

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. CRW-2723 Browser tab of started workspace has `che-Eclipse Che` name on CRW with Devworkspace engine enabled

          • 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
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CRW-2475 Dev Spaces 3.0 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

          Bug - A problem that impairs or prevents the functions of the product. CRW-2718 In CRW workspace, On git push command, Title is displaying as "Eclipse che" instead "CodeReady workspaces"

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          links to

          Web Link Identify and deliver minimal administration guide, installation guide, and user guide to migrate to che-docs main branch #21264

          Activity

            People

              dnochevn Dmytro Nochevnov
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: