Skip to content
Snippets Groups Projects

Resolve "Rename the `Master` role to `Maintainer`"

Merged Mark Chao requested to merge 42751-rename-master-to-maintainer into master

EE port at https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5948

Follow up (changes for backend): https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19413

What does this MR do?

Rename permission name "Master" to "Maintainer", from user's perspective.

No need to worry about API because it does not use permission level names, but level number.

  • EE check for ProjectCreationLevel|Masters and Developers + Masters and so on...

Are there points in the code the reviewer needs to double check?

Internal method call/constant changes are in the followup MR, because:

  • reduce probability of conflict
  • separate the safe changes from risky changes, so we can rollback risky changes in case something goes wrong, but keep safe changes.

Why was this MR needed?

See #42751 (closed)

Screenshots (if relevant)

CapturFiles_2

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Closes #42751 (closed)

Edited by Mark Chao

Merge request reports

Pipeline #23315383 passed

Pipeline passed for dd42cab9 on 42751-rename-master-to-maintainer

Test coverage 75.62% (0.00%) from 2 jobs
Approval is optional

Merged by Sean McGivernSean McGivern 6 years ago (Jun 6, 2018 3:00pm UTC)

Merge details

Pipeline #23331369 passed with warnings

Pipeline passed with warnings for e9ad837c on master

Test coverage 75.62% (0.00%) from 2 jobs

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
Please register or sign in to reply
Loading