[Task]: Permit or provide version evaluation channels.

[RokeJulianLockhart]

Description

1. Proposition

   An example of a similar FR is [Task]: Add new "enterprise" channel in devhub #14849 (comment), a counterpart of which – [Task]: Auto-approve add-on versions in the enterprise channel #14853 (comment) – requests, identically, that versions be publishable without review nor wait:

   Versions in the enterprise channel should be auto-approved, and scanner actions (like flagging, auto-approval delays) should never be triggered for them.

2. Rationale

   As stated at discourse.mozilla.org/t/addon-beta-test-versions/72373/4:

   I ask because like how I can utilize beta channels in the Google Play Store to use updates to trusted applications that I otherwise would need to utilize Obtanium or F-Droid to acquire due to how long those updates sit in Google’s validation pipeline, I get updates to from the Chrome Web Store weeks quicker than I do on AMO.

3. Maintainability

   However, per [Task]: Add new "enterprise" channel in devhub #14849 (comment), I wonder whether your channel identification system is flexible enough:

   We should record it as a new channel (value 3, since 1 and 2 are taken by unlisted/listed).

   I would have expected this to be represented more in the manner undermentioned:

   Channels:
     - Newness:
       - 0 (Stable)
       - 1 (Beta)
       - 2 (Alpha)
     - Enterprise

   ...than with numeric identifiers:

   Channels: [1, 2, 3, 4, 5]

Acceptance Criteria

Milestones/checkpoints

Preview Give feedback

1. Extension publishers can publish versions to a beta and/or alpha (etcetera) channel without delay.

Checks

• If I have identified that the work is specific to a repository, I have removed "repository:addons-server" or "repository:addons-frontend"

┆Issue is synchronized with this Jira Task