GitLab Acceleration Initiative meeting on 22 February, 2023

hestenet → credited markdorison → .

Transcript

0️⃣ Who is here today? Comment in the thread below to introduce yourself!

1️⃣ Do you have any topics to propose for the meeting today? Feel free to propose them in this thread, and then I will give them their own unique threads for discussion. Conversation moving slow? Go ahead and open your own thread in the next numeric order.

2️⃣ Scheduling: DA has a staff retreat on Mar 8 during our next initiative check-in - does someone else want to run the meeting? Otherwise we will skip.

3️⃣ GitLabCI default template issues have been broken out in the issue queue for the current template work: https://www.drupal.org/project/issues/gitlab_templatesThis → template has had some amount of testing recently and is now in pretty decent shape, but there are a few issues marked 'major' which need resolution.

4️⃣ The GitLab service degradation that was caused by this data integrity problem creeping in has been resolved in the most recent release: https://gitlab.com/gitlab-org/gitlab/-/issues/387980This means we can now look back into expanding the AWS cluster to improve performance.

5️⃣ We've had some movement on getting D9(soon to be  D10) pieces of drupal.org deployed (events.d.o was relaunched last week)Why is this important?The new credit content type that @fjgarlin has built so we can preserve credit on GitLab issues is in D9(And also work needed for Project Browser initiative is in D9) Getting those deployable will have us one step closer to the issue migration.

6️⃣ We still need to do much more to ensure D7 testing is supported, both by the template ( #3343810: Support for testing Drupal 7 with the template → ) and by the CI environments that are used in testing. (edited) 

Automatically closed - issue fixed for 2 weeks with no activity.