Roadmap 22.

[terabytesoftw]

• Update to the latest master branch.
• Add branch 22 to all yii2-extensions.
  • yii2-bootstrap5
  • yii2-debug
  • yii2-faker
  • yii2-gii
  • yii2-symfonymailer
  • yii2-mongodb
  • yii2-httpclient
  • yii2-twig
  • yii2-redis
  • yii2-authclient
  • yii2-elasticsearch
  • yii2-bootstrap4
  • yii2-bootstrap
  • yii2-jui
• Update templates yii2-app-basic, yii2-advanced and put them into operation with the 22 branch.
  • yii2-app-basic
• Apply Rector to clean up dead code from versions previous to PHP 8.2.
• Enable StyleCI for the 22 branch if possible.
• Integrate PHPStan for static analysis, configuring a baseline to allow progressive improvements over time.
• Once the branch is clean, we will make an initial release of the 22 branch along with all official extensions, providing a stable starting point without breaking changes.
• Gradually apply improvements and review pending PRs to determine what can be safely merged into 22.

[nadar]

good news! 🥳

[rob006]

Is there any explanation why there is 22.0 branch in this repo?

[nadar]

Sorry to jump in, but I’m a bit confused. Does this mean we’ll need to change our composer.json constraint to ^22.0 (or even ^2.22) instead of ^2.0? From the perspective of an everyday developer who isn’t deep into Yii2, that feels counter-intuitive. Why not just release 3.0 and keep things straightforward?

Yii has used a somewhat unconventional versioning scheme before—nothing inherently wrong, but it hasn’t been strict SemVer. It seems like now would be a perfect moment to clean that up rather than continue the old pattern.

[schmunk42]

Given this discussion, I'd go with 22.x.x (only three tuples, not 4 by default) with the option to release another major as 23.x.x.
This would also be semver, I think.

[samdark]

@schmunk42 yes. First release for all these will be 22.x.x.x

[samdark]

@nadar Yes. That is intended, ^2 won't match ^22. These versions have no strict backwards compatibility (but still very close). 3.0 doesn't work since initial version for extensions can't be 3.0 as I've pointed out above.

[samdark]

@schmunk42 three tuples i.e. 22.x.x, 23.x.x should work well.