At DrupalCon Vienna, we opened the opt-in period for module maintainers to volunteer their modules to be migrated to GitLab issues. You can opt yours in at #3409678: Opt-in GitLab issues.
That means that we will have some projects with issues on Drupal.org and some other projects with their issues on GitLab during this transition period. Due to this, some things will change in our current systems.
Changes to Drupal.org
The issue cockpit on each project's page will go away. The current issue cockpit that will see in projects reads data from our internal issues, but as projects transition to GitLab issues this block no longer makes sense. We will replace this for a simple "Issues" link that will take you to the right issue queue, whether it is GitLab or Drupal.org.
Parent and related issues will now be connected via a full URL. It used to be connected via entity reference fields, pointing at internal issues. Now that we have two systems for this, these will be links, that once rendered will bring the metadata information, like title and issue status, as we did with internal issues. We will be able to link both Drupal.org and GitLab issues into these new fields, and the old entity reference fields will go away.
What's next?
We ask project maintainers to help us at the Drupal Association iterate and improve on this process as we migrate more and more projects. We know that change can take time to be adopted, and we are really excited to help project maintainers move their issues into GitLab.
There are almost 200 projects with more than 1000 issues, and around 2000 projects with more than 100.
Drupal "core" has more than 115K issues.
The roadmap will be (in each iteration, we will address feedback, fix bugs...):
- Migrate projects that opted in
- Make this the default for new projects
- Migrate low-risk, low-usage, and/or sandbox projects
- Migrate remaining projects, excluding a few selected high-volume, high-risk
- Migrate the rest of the projects, including core
We are very excited about this transition, and we truly think it will be an improvement to the contribution experience. We are also thankful to the community for helping us with this.