Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.During the last DIWG meeting we discussed the need to clean up infra issue queue. It has way too many components, with most of the issues being in "Other". Suggesting that the many components we have are not necessary the right ones. Today Rudy and I looked through the 'Other' queue and here is the final list of components we came up with.
Blocked IPs
Continuous Integration (e.g. Jenkins related issues)
Development Environments (for dev sites requests etc.)
Git
Packaging
Monitoring (e.g. loghost)
Servers (for issues currently in Database, File server, Mail, Operating System, VMs, Solr, Webserver)
Updates System (updates.drupal.org and other related issues)
IRC
Other
---
Remove components:
api.drupal.org - move to https://drupal.org/project/apidrupalorg
BZR 1
CVS 0
Drupal.org module 25 (D.o customizations)
Drupal.org theme 3 (Bluecheese)
PHP 1
SEO 2
Metrics (Move to drupalorg / project)
association.drupal.org 3 (own queue)
docs.drupal.org 0
groups.drupal.org 3 (own queue)
qa.drupal.org 10 (own queue)
redesign.drupal.org 1
security.drupal.org 1 (own queue)
drupalcode.org - combine with Git
Association intranet 0
driphop.drupal.org 0
We'll have to move some issues manually. But for some we can use script, similar to the one I used in #1848862: Write sql script to move issues out of Webmasters queue.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 2207117-5-83019aa-infrastructure-cleanup.patch | 5.93 KB | Mixologic |
Comments
Comment #1
tvn CreditAttribution: tvn commentedSince there were not objections during the past 2,5 weeks, we'll go ahead with this plan. basic can you start on this? I'll see if I can help later.
Comment #2
tvn CreditAttribution: tvn commentedComment #3
tvn CreditAttribution: tvn commentedHere is example hook_update to move issues between queues #2256249: Move 'Project ownership' issues to the new queue
Comment #4
MixologicComment #5
MixologicOkay, finally got all the environments configured and working.
Here's the patch that should clear out all the infrastructure components that we dont need, moves issues to other queues, and consolidates many into the 'servers' bucket.
I refactored after a ton of cut n paste to make a utility function that we can use for future issue queue manglings (i.e. things like move all the things tagged "licensingissues" to the licensing queue)
Have a looksee. I ran it on my local dev and caught the small bugs.
Comment #6
drummComment #8
drummComment #11
drummThis is now deploying. The infrastructure issues themselves will be updating as the update runs. The issue queue Views will catch up as Search API indexes at the end.
Comment #12
MixologicComment #13
tvn CreditAttribution: tvn commentedI talked to jhodgdon, and she was fine with moving api issues to apidrupalorg queue. I moved 3 open issues and removed component. There are 49 closed issues with this component still. Next time we move some issues around somewhere, we should move these too.