What should be in the next stable release of Schema.org Metatag for D9 & D10?

Comments

DamienMcKenna created an issue. See original summary.

damienmckenna’s picture

Version: 8.x-1.x-dev » 8.x-2.x-dev
vipin.mittal18’s picture

Hello DamienMcKenna,

Do you have any tentative date for alpha/beta release against this 8.x-2.4 dev version?

Thanks
Vipin Mittal

rajeshreeputra’s picture

Status: Active » Reviewed & tested by the community

All issue from child issue list seems to be fixed and also D10 porting/readiness work also completed so RTBC for the 8.x-2.4 or 3.0 release.

I am in favor of 3.0 release instead of 8.x-2.4 as D10 work will also be released in new release.

damienmckenna’s picture

Thank you for reviewing the current codebase.

There is no reason to create a new major release just to mark compatibility with D10, see https://medium.com/jakob-on-drupal/dont-go-making-major-version-changes-... for further details.

We'll do a new v3.0 branch for compatibility with Metatag 2.

malik.kotob’s picture

Hi @DamienMcKenna! Echoing Vipin's comment above, are there any outstanding tasks you could use support on that are blocking a D9/D10 2.4 release?

claudiu.cristea’s picture

Priority: Normal » Major

As many modules depend on schema_metatag and they want to release D10 compatible versions too, I think we should do it as soon as possible. The CI/CD used in my projects is not allowing modules in dev-* state, so I need to depend only on stable versions and the D10 change is too big to be used as a patch. As D10 is 3 weeks away, I think it's the right time for 2.4. Thank you!

damienmckenna’s picture

There's one outstanding bug that could use some work, could someone please take a look at #3192117? Thank you.

rajeshreeputra’s picture

@DamienMcKenna, Looks like there is MR created could you please verify.

vipin.mittal18’s picture

@claudiu and I are in agreement. We would appreciate it if you could proceed with the pre-release version at least.

damienmckenna’s picture

damienmckenna’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

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