Bulk update Experience Builder issues to Canvas issues

The main thing I’ll want here is the copyediting for the comment that’s posted. Something along the lines of:

Drupal Canvas is the new name for Experience builder. See more details at [issue or other link]

@drumm: Would it be possible to:

1. Bulk-move issues? (I think that's what this issue is about, but I've not been privy to any conversations, and this issue summary doesn't really say that — it might just as well mean that we're supposed to move 'em manually?)
2. Bulk-move issue forks/MRs? We currently have 219 open MRs: https://git.drupalcode.org/project/experience_builder/-/merge_requests 😅

I'd recommend following as the comment because we will be making a broader public announcement later:

Experience Builder has been renamed to Drupal Canvas in preparation for its beta release. You can now track issues on the new project page here → .

Would be possible to rename canvas → canvas_old and experience_builder → canvas?
I can see canvas only had alpha/dev releases for 7.x-1.0, so existing releases shouldn't be a blocker.

Depending on how gitlab projects are associated with d.org projects (I don't know the internals), this might simplify things a lot, both on the DA and the (formerly) XB team.

Bulk-move issues? (I think that's what this issue is about, but I've not been privy to any conversations, and this issue summary doesn't really say that — it might just as well mean that we're supposed to move 'em manually?)

That’s totally possible and what this issue is planning.

Bulk-move issue forks/MRs? We currently have 219 open MRs: https://git.drupalcode.org/project/experience_builder/-/merge_requests 😅

That’s not quite practical to do. Each issue that has code worked on after moving will want a fork of the new project. Assuming the whole commit history is moved, you can add both issue forks as remotes and merge/rebase code around. Theoretically we could automate making the equivalent forks and push branches around, but that would be a bit of effort to implement. And then when https://git.drupalcode.org/project/experience_builder/-/merge_requests/1483 lands, Git will likely be a wall of merge conflicts, so manual work, or a more-sophisticated automation will be needed.

Would be possible to rename canvas → canvas_old and experience_builder → canvas?

No. We do not rename projects. Existing releases and repositories are guaranteed to be indefinitely available, so we aren’t breaking people’s site builds. Renaming would be a lot more complexity, not at all a simplification.

Understood. Thanks!

Rename is complete: #3543402-40: Replace Experience Builder name everywhere → .

https://www.drupal.org/project/canvas/releases/1.x-dev → and https://www.drupal.org/project/canvas/releases/1.0.0-alpha1 → are live, so ready for bulk move 👍

Do we want to move closed issues too, or just open issues?

I recommend creating the 0.x-dev release for canvas before bulk updating issues. This will allow issues with the 0.x version to have that option available once moved.

https://www.drupal.org/project/canvas/issues/3439664 🌱 [later phase] Research Issue For Workspaces Extra Postponed is the test issue for final review before I start the bulk update. Note the version field would need to be updated on the next issue update. Assuming the version was 0.x-dev, adding the release will fix that.