>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3554242. --> Reported by: [valthebald](https://www.drupal.org/user/239562) >>> <p>Followup to <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai/issues/3546657" title="Status: Closed (fixed)">#3546657: [Meta] Move out submodules</a></span></p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>When moving submodules to their own projects on drupal.org, we need to take care of existing installations.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Use <a href="https://www.drupal.org/about/core/policies/core-change-policies/how-to-deprecate-and-remove-an-extension">core change policy</a> as a base: </p> <ol> <li>Mark submodules as deprecated in the current major version (1.3.x). That probably means we'll need 1.3 release somewhere in advance before 2.0. Deprecating submodules could be the only change from 1.2, so we can do this quite fast</li> <li>Have stable releases of submodules (should they all have 1.3.0 version, or it's not necessary?) by the time of 1.3.0</li> <li>Remove submodules from the code in 2.0.x</li> </ol> <p>Reference issues for removal of "seven" theme from core: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/3278212" title="Status: Closed (fixed)">#3278212: [Meta] Tasks to deprecate Seven</a></span>, <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/3278331" title="Status: Closed (fixed)">#3278331: [Meta] Tasks to remove Seven from core and move to contrib</a></span></p> <h3 id="summary-proposed-resolution">Alternative option</h3> <p>One suggested alternative is to remove the modules already in 1.3.x, replacing them with submodules' dependencies in composer.json</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ol> <li>Decide which flow to follow</li> <li>If we choose the core flow, create issue to deprecate a module for every module being removed in 2.0.x</li> </ol> > Related issue: [Issue #3552884](https://www.drupal.org/node/3552884) > Related issue: [Issue #3552885](https://www.drupal.org/node/3552885) > Related issue: [Issue #3552887](https://www.drupal.org/node/3552887) > Related issue: [Issue #3552888](https://www.drupal.org/node/3552888) > Related issue: [Issue #3552904](https://www.drupal.org/node/3552904)