Features aren't just code, they are an experience. During code review, it's unreasonable to expect reviewers to provide a guarantee that the code has no bugs or is of sufficient quality. It's also unreasonable for the author to have this level of quality since expectations are different depending on the user.

We can add an experimental mode to Coder that enables us to try the new functionality, continue to make releases, and still make it available to the public.

This can be a command-line flag: coder server --experimental, and an env var: CODER_EXPERIMENTAL. This can be included in the buildinfo response and should be used in the site and API.

A solid example for where this could add value is the template emoji feature. There were a few bugs that appeared after we tested it more thoroughly internally, but we would not want to slow down development. This could have been flagged under experimental mode for a few days, tested internally, then exposed to the public.

The onus is on the feature creator to move functionality out of experimental mode.