Rename Feature - Browser-based DAST to DAST
This MR renames Browser-based DAST to DAST.
Why is this change being made?
We have two DAST features in the Dynamic Analysis group today, Proxy-based DAST (ZAP), and Browser-based DAST (proprietary). In 17.0, Proxy-based DAST is being removed. Since we will only have 1 DAST offering going forward, we would like to simplify the feature name. This aligns with the following GitLab feature naming principles:
It should have as few words as possible
Reducing confusion as we re-factor existing features
Process
Process for Renaming Features (handbook)
Approvals
Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:
-
Chief Product Officer @david
(post MR link in chief-product-officer once all others have approved) -
PLT Leader relevant to the affected Section(s) @hbenson -
The Product Director relevant to the affected Section(s) @sarahwaldner -
The Engineering Manager relevant to the affected Section(s) @agroleau -
The Senior Engineering Manager relevant to the affected Section(s) @twoodham -
Director of Product Design @vkarnes
**Note:**_ Chief Product Officer approval should be requested once all other approvals have been completed. To request approval, post the MR link in the #chief-product-officer channel tagging @david
and cc'ing @Gena Schwam
._
The following people need to be on the merge request so they stay informed:
-
Chief Technology Officer @sabrinafarmer -
Development Leader relevant to the affected Section(s) @bmarnane -
VP of Infrastructure & Quality Engineering @meks -
VP of UX @ampesta -
Director of Technical Writing @susantacker -
Engineering Productivity @gl-quality/eng-prod -
The Product Marketing Manager relevant to the stage group(s) @dsteer
After Approvals and Merge
-
Create an issue in the gitlab-org/quality/triage-ops
project to update GitLab Bot automation:- for Category change
- for Stage or Group change
- If label migration is required, please follow the self-serve instructions to get started on a one-off label migration MR
-
Open an MR in the gitlab-org/gitlab
project to update any reference of the previous group label to the new one -
Mention the product group Technical Writer to update the documentation metadata -
Share MR in #product
,#development
, and relevant#s_
,#g_
, and#f_
Slack channels