Skip to content

Update Package maturity targets

Tim Rizzi requested to merge trizzi-master-patch-55852 into master

Why is this change being made?

As per Product#1372 (closed) this MR updates the category maturity targets for the Package stage.

  • Dependency Firewall: Originally we were targeting July 2020, but we were not able to hit this date. Our current plan is to first expand the Dependency Proxy to support Maven packages and then to start adding MVC Dependency Firewall features that will focus on preventing suspicious packages from being downloaded from remote registries.
  • Jupyter Notebooks: We are not currently prioritizing any work for Jupyter and so I set the date further out.
  • GitLFS: @jramsay I'm not sure what features are required for moving LFS up in maturity? For now, I pushed the date back and maybe we can create an issue that will define the maturity targets for this category?

Author Checklist

  • Correct MR template applied (e.g blog post)
  • 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

Merge request reports