Skip to content

WIP: Update Secure workflow with training feedback

Olivier Gonzalez requested to merge update_secure_workflow_with_training_feedback into master

WIP

To avoid change fatigue and since there are other upcoming changes to the workflow, we should not merge this MR right now even if approved. I'll do one bulk update with other changes.

Why is this change being made?

After going through a stage wide training the Secure team members have provided feedback about the Secure workflow. This MR is addressing some of them:

  • move workflow to its own page
  • add usage of workflow::refinement
  • clarify planning breakdown vs refinement
  • add links to videos about how to work with issues board
  • rename backlog refinement to engineering refinement
  • add new refinement labels usage to the process

Approvals

As this MR is impacting the workflow of several teams and as we look for the adoption of these changes, it will require a minimal consensus.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack

Edited by Olivier Gonzalez

Merge request reports