Problem/Motivation

There are some projects with stable releases that are Drupal 10 compatible but they show up as dev-only. So far these have all been with this version: >=9.1

Steps to reproduce

Example:

https://www.drupal.org/project/migrate_tools
https://dev.acquia.com/drupal10/deprecation_status/projects/migrate_tools

Proposed resolution

Update the logic to handle these cases.

Remaining tasks

  1. Update the logic
  2. Test and release

User interface changes

Information will be correct.

API changes

Data model changes

Comments

Kristen Pol created an issue. See original summary.

kristen pol’s picture

Forgot to add screenshots.

kristen pol’s picture

Just realized the screenshots don't match up (2 different projects) but both projects have the same issue and same version so I won't upload a new screenshot.

kristen pol’s picture

gábor hojtsy’s picture

Wow, yeah this update fixes some things, good catch.

Using the Semver class instead of our regex for stability checking the following changes happen with the last #143 resulset:

- Make tagged release available status down from 526 to 481
- Improve stability of release status up from 198 to 206
- Stable, congrats status up from 726 to 763

Good catch!

  • b88ce0e committed on 8.x-5.x
    Issue #3304033 by Kristen Pol, Gábor Hojtsy: Data updates for stable...
gábor hojtsy’s picture

Status: Active » Fixed

Drupal.org does not connect commits in non-standard branches to issues. The script commit is in https://git.drupalcode.org/project/deprecation_status/-/commit/3541d962c...

gábor hojtsy’s picture

Also deployed the new dataset to dev.acquia.com now.

kristen pol’s picture

Thanks for the quick fix! Looks good :)

Status: Fixed » Closed (fixed)

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