Skip to content

Draft: Add technical detail to Cloud Seed announcement in the 15.5 release post

Brian Rhea requested to merge cloud-seed-release-post-announcement into master

Why is this change being made?

This MR addresses @sytses's feedback on the 15.5 release post draft:

The Cloud Seed text feels too vague for a release post, it is lacking technical detail. Explain it is to enable a simple experience while enabling gradual customization. Based on Terraform. Using managed services.

Why a separate MR?

Normally, we would simply integrate feedback to the release post MR, but because this announcement mentions Google Cloud, additional legal review is required.

We will incorporate feedback on this MR, submit for a legal review, and merge upon approval. The text in the current draft has been approved by both GitLab and Google's legal teams and the publication of the 15.5 release post will proceed with that text.

The release post will be published in 2 days and expected review from Google is 7 working days, so the revisions made here will likely be added to the post after publication.

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • 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 affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Brian Rhea

Merge request reports