- Issue created by @phenaproxima
- 🇺🇸United States phenaproxima Massachusetts
@drumm fixed the permanence issue in ✨ Fetch CI artifact for Drupal CMS packaging Active , and that allowed us to tag RC2. So it is done!
@pameeela, @tim.plunkett, and I agreed that Drupal CMS should have an RC2 release that uses the impending Drupal core 11.1.0.
I'd say RC1's release went surprisingly well, considering that it was the first time the subtree split infrastructure kicked on and started doing its thing. Our product is now officially Composer-managed. One sore spot, though, was the pre-built zip file. For DrupalCon Singapore, the DA simply created a redirect to the CI job artifact, which accidentally got wiped out in a cleanup spree (see 🐛 Our CI artifact generation is messy and wasteful Active ). Having a long, ugly link to a CI artifact which can be deleted is not a long-term solution to offering stable release links. We need to do better for RC2.
One possibility is for the DA to engineer something that would grab an artifact when you make a release node, and store it permanently. GitLab has a stable artifacts API which presents reliable URL for getting job artifacts. So let's say we agreed on a magic name for a particular CI job -- maybe drupal.org release or similar -- whose job artifacts, if downloaded as a whole, are what should be safely stored by drupal.org and permanently attached to the release node for a particular branch or tag.
According to GitLab's documentation, that artifact would be available at a consistent URL (assuming that the tag is 1.0.0-rc2): https://git.drupalcode.org/api/v4/projects/157093/jobs/artifacts/1.0.0-rc2/download?job=drupal.org+release (157093 is our GitLab-generated project ID, which is a constant.)
To me, this seems like a reasonable solution to offering stable downloads of our releases, if indeed that's something we want to do. Indeed, we only really need to do this if we want to offer people a ZIP file to download, which is an assumption that
🐛
Installing Drupal CMS with the zip file does not grab the latest version of dependencies
Active
calls into question. If we instead require people to use composer create-project drupal/cms:1-rc2 (or its DDEV equivalent, ddev composer create drupal/cms:1-rc2), then it's not entirely clear why we'd need to offer a zip fie at all. I raised that point in
🐛
Installing Drupal CMS with the zip file does not grab the latest version of dependencies
Active
.
In any case, tagging RC2 should be quite straightforward now that the subtree split infrastructure is in place. We should probably:
Active
General
@drumm fixed the permanence issue in ✨ Fetch CI artifact for Drupal CMS packaging Active , and that allowed us to tag RC2. So it is done!