Remove references to Beta status in product and docs

Goal

Reflect the non-Beta status of the Web IDE after 16.0.

Tasks

• Update the product UI to reflect the non-Beta status of the Web IDE after 16.0 release.
• Review all GitLab documentation related to the Web IDE, including user guides, tutorials, and developer documentation, to identify references to the Beta classification.
• Edit documentation to remove references to the Beta classification, including any language or phrasing that implies that the Web IDE is still in Beta.
• Update screenshots in documentation to reflect the non-Beta status of the Web IDE.
• Verify that all links and cross-references in the documentation related to the Web IDE are up-to-date and accurate.
• Conduct a final review of all documentation changes to ensure that all references to the Beta classification have been removed.
• Publish the updated documentation to the GitLab website.
• Notify GitLab users and customers that the Web IDE is no longer in Beta status via release notes, blog posts, or other communication channels.
• Monitor feedback from users and customers to ensure that the removal of the Beta classification has been well-received and that there are no outstanding issues related to the status change.

added to epic &7683

added Category:Web IDE GitLab Free devopscreate groupeditor [DEPRECATED] typemaintenance labels

added sectiondev label

changed the description

@oregand this is some cleanup for 16.0. Should be fairly simple.

changed milestone to %16.0

set weight to 1

added Deliverable documentation maintenancerelease workflowready for development labels

changed the description

@pslaughter @ashrafkhamis

Do y'all feel comfortable picking this up in tandem for %16.0 ?

Do y'all feel comfortable picking this up in tandem for %16.0 ?

@oregand, yes! Let's do it

@oregand @ericschurter @pslaughter Yes, it's a bit more complex on the docs side. We have many references to Web IDE (old) and Web IDE Beta (new) as well as some cross-linking. I think the best way to go about it would be to somehow merge these two pages:

• https://docs.gitlab.com/ee/user/project/web_ide/
• https://docs.gitlab.com/ee/user/project/web_ide_beta/

Depending on how much of https://docs.gitlab.com/ee/user/project/web_ide/ is now supported by https://docs.gitlab.com/ee/user/project/web_ide_beta/, it could be more of a lift and shift.

@pslaughter

To help lighten the load on your end, I am going to pick this up as part of Documentation for new Web IDE experience (&7693 - closed). I will pull you into the reviews to ensure we're aligned but your time is better spent on the actual coding

assigned to @pslaughter

added Technical Writing docsimprovement labels

This issue made it to workflowready for development without the addition of a frontend or backend tech stack label. Both will be assigned as a result. Bot policy.

added backend frontend labels

mentioned in issue gitlab-com/Product#5630 (closed)

changed epic to &7693 (closed)

assigned to @oregand and unassigned @pslaughter

mentioned in merge request !117778 (merged)

Setting health status to on track as the milestone has just begun.

Issue participants are welcome to override this by setting the health status to another value.

changed health status to on track

added groupide label and removed groupeditor [DEPRECATED] label

mentioned in issue gitlab-org/quality/triage-reports#12166 (closed)

mentioned in issue gitlab-org/quality/triage-reports#12229 (closed)

added quad-planningcomplete-no-action label

@oregand This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

/cc @ericschurter

This is done

closed