Plan for initial codebase

Migrated issue

Reported by: jonathan1055

Related to !24 (merged) !31 (merged) !17 (merged) !8 (merged) !14 (merged) !13 (merged)

Problem/Motivation

This project needs to cover several key set-ups of Contrib projects, to help us increase test coverage. This will need several branches, which may not differ by much. We can use the recognised version naming conventions as in regular contrib projects

Proposed resolution

Testing with Drupal 7

  1. Branch 7.x-1.x which does not contain a composer.json file
  2. Branch 7.x-2.x which does contain a composer.json file

Testing with Drupal 10

  1. Branch 3.x - which is also compatible with Drupal 9
  2. Branch 4.x - which is only also compatible with Drupal 10+

Within each branch, the .gitlab-ci.yml can define variants to test with the minimum and maximum PHP versions for the core releases being used.

MR testing branches

This issue is closed but the test branches are still used. These can be draft Merge Requests, but also the workflow is now set to run a pipeline if the branch name starts with 3503337 so this avoids the need to create MRs

Related issue: Issue #3503426

Edited by drupalbot