Problem/Motivation

The Entity Activity project currently has only the 8.x-1.x development branch. Issue #3287201 is completing Drupal 10 compatibility on that branch, while Drupal 11 support requires additional API changes that should not complicate the Drupal 10 compatibility fix.

Issue #3211106 previously requested a 2.x branch for Drupal 9, but that target is now obsolete. This issue updates the request for the currently supported core versions.

Proposed resolution

After #3287201 is committed, create a 2.x development branch from the completed Drupal 10-compatible code. Use that branch for Drupal 10 and Drupal 11 compatibility work and for future development.

The initial 2.x work should:

  • retain Drupal 10 compatibility;
  • add and verify Drupal 11 compatibility;
  • run the project PHPUnit test suite in GitLab CI for supported core versions;
  • document any intentional API or data-model changes.

Remaining tasks

  • [x] Complete and commit #3287201 for Drupal 10 compatibility.
  • [x] Maintainer: create the 2.x branch from the completed Drupal 10-compatible revision.
  • [x] Open a separate Drupal 11 compatibility issue and merge request against 2.x.
  • [x] Add GitLab CI coverage for the supported Drupal core versions.
  • [x] Decide whether #3211106 should be closed as superseded by this issue.

User interface changes

None expected.

API changes

None in this planning issue. Drupal 11 compatibility changes are described in their implementation issue.

Data model changes

None.

Comments

ivrh created an issue. See original summary.

ivrh’s picture

ivrh commented

@flocondetoile, merge request !11 has been merged and the canonical 2.x branch has now been created from that Drupal 10-compatible revision.

  • Phase 1 is ready in MR !12: Unit and Kernel tests plus an enforced 80% production-PHP line-coverage gate.
  • The hosted GitLab pipeline #963175 passes at 98.05% coverage, including the existing document-root and /web/ browser-test layouts.
  • The existing lint failures remain non-blocking in this MR and will be handled next in child issue #3623437.
  • After the lint baseline is clean, I propose a separate Drupal 11 compatibility issue and MR against 2.x, targeting ^10.3 || ^11 and adding the supported-core CI matrix.

I also reviewed PaCSON's existing compatibility patch. Most of it is already upstream through the Drupal 10 work; the remaining Drupal 11 work should be ported selectively rather than applying that aggregate patch wholesale.

ivrh’s picture

ivrh commented
Version: 8.x-1.x-dev » 2.x-dev

The 2.x release line is now available:
- [2.x-dev](https://www.drupal.org/project/entity_activity/releases/2.x-dev)
- [2.0.0-beta1](https://www.drupal.org/project/entity_activity/releases/2.0.0-beta1)

MR [!13](https://git.drupalcode.org/project/entity_activity/-/merge_requests/13) has been merged after the merge-train pipeline passed. This issue is now retargeted to 2.x-dev.

The beta is explicitly marked as a testing release, has not yet received broad real-world testing, and is not recommended for production use. Testers and compatibility reports are welcome. Drupal 11 compatibility remains planned follow-up work and is not claimed by beta1.

ivrh’s picture

ivrh commented
Issue summary: View changes
Status: Active » Fixed

The 2.x plan is complete.

  • #3287201 was committed and is Fixed.
  • The canonical 2.x branch was created and is available as 2.x-dev.
  • MR !12 added blocking test and coverage gates; MR !13 established the clean blocking validation baseline; and MR !14 added Drupal 11 support while retaining the Drupal 10.3 minimum.
  • The final 2.x pipeline #964957 passed at 294ce4c0c17637a411214586a12679edbd485e91 with 845 tests and 97.96% production PHP line coverage.
  • The obsolete Drupal 9 branch proposal #3211106 is Closed (outdated).

2.0.0-beta2 is published as the first Drupal 11-compatible beta. No in-scope work remains. Marking Fixed; version remains 2.x-dev.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.