VerifyEmail 1.x will be maintained through the end of 2024 (coincide w/ Symfony 5.4 EOL && PHP 8.2 EOL)
VerifyEmail 1.x will transition to security fixes only soon-ish. I believe this is safe considering the stability demonstrated since the bundles inception.
VerifyEmail 2.x will be the default branch for the repo, all new features will be merged into 2.x. This would happen sometime after we merge #157
Changes:
bumps PHP minimum 8.3. When 1.x reaches EOL in November-ish 2024 (EOL for Symfony 5.4). PHP 8.2 will be security fixes only. PHP 8.4 is due out 2024. Setting 8.3 as the minimum feels "bleeding-edge" but I think this is ok with the release cadence of PHP and our timing with a 2.x branch.
Dropping Symfony 5.x with a minimum 6.4.5 which is the current LTS.
[ ] CI Config changes to allow for dropping PHP Versions
Assumes the following:
1.xwill be maintained through the end of 2024 (coincide w/ Symfony 5.4 EOL && PHP 8.2 EOL)1.xwill transition to security fixes only soon-ish. I believe this is safe considering the stability demonstrated since the bundles inception.2.xwill be thedefaultbranch for the repo, all new features will be merged into2.x. This would happen sometime after we merge #157Changes:
8.3. When1.xreaches EOL in November-ish 2024 (EOL for Symfony 5.4). PHP 8.2 will be security fixes only. PHP8.4is due out 2024. Setting8.3as the minimum feels "bleeding-edge" but I think this is ok with the release cadence of PHP and our timing with a2.xbranch.Dropping Symfony
5.xwith a minimum6.4.5which is the current LTS.[ ] CI Config changes to allow for dropping PHP Versions