Public release checklist

To release publicly, we need:

• Complete all of the requirements to open-source a project - #50 (closed) (from the handbook)
• Sign off from legal - https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/2264
• Integration with pypi.org in the pipeline
  • Configure semantic-release to publish the pkg there
• Blog post approval - https://gitlab.com/gitlab-com/marketing/brand-product-marketing/content-strategy-and-ops/blog/-/issues/203 / doc

Then to kick off: 🚀

• Create a prod account on pypi.org
• Create an API Token on pypi.org
• Create the CI/CD variable: $PYPI_TOKEN
  • Store the var as protected & masked
• Merge the following MR: !85 (merged) (29th October NZT)
  • semantic-release automatically pushes package to pypi.org & gitlab package registry
• Manually make the project public
• Ensure everything looks as expected
  • package is published on gitlab package registry, pypi.org, links in main doc are valid etc.
• Publicize the blog - Set for release on 29th October PDT
• Notify relevant Slack channels of release