>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3493414. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) >>> <p>Drupal CMS is unlike most other Drupal things -- it has no APIs or update path. So what, exactly, does alpha/beta/RC/stable mean in the context of this project? We need to define these as a matter of policy.</p> <p>To start discussion, I propose the following:</p> <ul> <li><strong>Alpha</strong>: not something we do. We don't ever have to tag an alpha; since we have no update paths or APIs, it doesn't mean much from a stability perspective.</li> <li><strong>Beta</strong>: "early preview" -- nothing in a beta is guaranteed to make it into the next release. Dependencies may be patched, or using dev branches.</li> <li><strong>Release candidate</strong>: in an RC, the set of recipes in it is finalized. No recipes will added or removed unless they are secondary dependencies. Modules/themes may still be added or removed, and functionality may change to some degree during this phase. Dependencies must be tagged and cannot be patched.</li> <li><strong>Stable</strong>: no recipes or secondary dependencies are added or removed. Functionality doesn't change, apart from what's needed to fix buggy behavior.</li> </ul> > Related issue: [Issue #3447882](https://www.drupal.org/node/3447882)