Skip to content

Update Package direction February

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

Why is this change being made?

This MR updates the Package direction page for February 2024. Highlights:

  • The big change was making the dependency firewall portion real. Previously we had some ideas but now we have a proposed MVC+ that can be validated with customers.
  • I also updated what's next and why
  • Minor grammatical fixes

Please note that the maturity plans have also been updated based on our current capacity and roadmap:

  1. Dependency firewall moved back from April 2024 to September 2024. We will wait to implement this until after the npm dependency proxy has been completed in May/June 2024.
  2. Dependency proxy moved back from December 2024 to June 2025. Why? We've decided to accelerate development on the firewall and postpone adding dependency proxy support for NuGet and PyPI. The plan is to solidify the product for Maven and npm, including a working firewall and (possibly) virtual registry support for Maven and npm. This will allow us to signal to our enterprise customers that we are working to build a product that can replace Artifactory.
  3. Helm chart registry moved back from June 2024 to December 2024. The plan is to start using the container registry as a helm chart registry. But in terms of priority the container registry team is focused on the GA rollout, improving UX, and performance improvements. I hope we can work on this in the second half of 2024.

I didn't change the package and container registry maturity targets. If we can get to package cleanup policies, we can make it to Complete in August.

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

CHANGEME - add the details saying why, not just what.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • 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, and the content is SAFE
  • 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
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Merge request reports