We currently don't have an official mechanism to provide beta access to new package managers that haven't been implemented fully to be deemed officially supported and documented for our user base. While there is the --dev-package-managers flag that one can hardly be assumed being equivalent to beta functionality since there's no distinction on what such a package manager implements at a given time, in other words usage of that hidden CLI flag only denotes that the given package manager (ideally) doesn't immediately crash, but its state can vary between bare skeleton to almost finished waiting to be flipped to officially supported.
Giving users early access to package managers conforming to at least some MVP (minimal viable product) state is beneficial to enter faster feedback loop on the possible future enhancements directions we could take with it. Usually projects resort to cooking up new major beta releases, but adding a package manager doesn't necessarily need to mean a major version bump (certainly not with semver). At the same time though we need to keep rolling out regular releases, so there doesn't seem to be really space for beta releases and therefore this whole tech preview/early access thing would need to be handled solely on the documentation side of things.
We currently don't have an official mechanism to provide beta access to new package managers that haven't been implemented fully to be deemed officially supported and documented for our user base. While there is the
--dev-package-managersflag that one can hardly be assumed being equivalent to beta functionality since there's no distinction on what such a package manager implements at a given time, in other words usage of that hidden CLI flag only denotes that the given package manager (ideally) doesn't immediately crash, but its state can vary between bare skeleton to almost finished waiting to be flipped to officially supported. Giving users early access to package managers conforming to at least some MVP (minimal viable product) state is beneficial to enter faster feedback loop on the possible future enhancements directions we could take with it. Usually projects resort to cooking up new major beta releases, but adding a package manager doesn't necessarily need to mean a major version bump (certainly not with semver). At the same time though we need to keep rolling out regular releases, so there doesn't seem to be really space for beta releases and therefore this whole tech preview/early access thing would need to be handled solely on the documentation side of things.