### Context Over the past two years, GitLab and the GitLab community have added support for publishing and installing packages in a variety of [formats](https://docs.gitlab.com/ee/user/packages/). When a new format is released, there are frequently follow-up issues and bugs that are discovered that must be prioritized, developed, and released. ### Problem to solve The problem is, that as a small team, we often need to make difficult prioritization decisions based on customer impact. This means that the more popular formats like npm and Maven have been continuously improved, while the less frequently used formats have not. As a user or as a customer this can be really frustrating as you are left with a sub-optimal implementation that either prevents you from using the feature or forces you to use non-ideal workarounds. ### Proposal 1. Identify critical blocking issues for the Conan repository and add them to this epic. 1. Update the documentation to be transparent about these limitations and the current state of the feature. 1. Prioritize blocking issues to help GitLab customers reliably use the package registry. 1. Receive feedback and monitor usage to continue to prioritize and iterate on the feature. #### Benefits 1. By being transparent, customers can make informed decisions on whether or not they would like to adopt the feature. 1. Prior to adding new formats, we should ensure that our existing product works reliably and at scale.