Add testing configuration as an official task of a site moderator

Created on 15 September 2022, almost 3 years ago
Updated 11 April 2023, over 2 years ago

Problem/Motivation

Drupalci will automatically stop testing on old versions of Drupal core. This is intended, since those test runs are not useful anymore, especially for EOL versions of core or php.

However, this leaves an issue for those trying to get tests updated who aren't maintainers. Community members are no longer able to run tests on projects that have outdated configurations, and are unable to update them.

Since updating the configuration doesn't change the module's codebase, I propose that site moderators should be able to update or add tests configurations when they are out of date. This unblocks community members from being able to test their patches without needing to contact the maintainers to update the configurations.

By adding this to the official tasks of site moderators, community members will know they can ping a moderator in slack or create an issue in the site moderator's queue.

This proposal is making updating test configurations an official policy, rather than an unofficial one that has existed until now. Site moderators already have access to update tests, so no technical change is required to the drupalorg codebase.

Feature request
Status

Active

Component

Policy

Created by

🇺🇸United States japerry KVUO

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024