You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 2.0 is looking like it will be released in 2024. Version 1.x will be transitioned to security fixes only until it reaches its EOL in late 2024 / Q1 2025. New Features should be merged into 2.x unless absolutely necessary to preserve BC in 1.x
This issue will be updated to reflect any tasks required to get 2.0 out the door. Any issues concerning 2.0 should tag this thread / issue where appropriate.
Preface
2.x
branch is NOT production readyVersion
2.0
is looking like it will be released in2024
. Version1.x
will be transitioned to security fixes only until it reaches its EOL in late 2024 / Q1 2025. New Features should be merged into2.x
unless absolutely necessary to preserve BC in1.x
This issue will be updated to reflect any tasks required to get
2.0
out the door. Any issues concerning2.0
should tag this thread / issue where appropriate.Todo's for release
annotations
UPGRADE.md
to document path's forward to BCCHANGELOG.md
for 2.x#[SensitiveParameter]
attributes for any secrets - prevent leaking sensitive data in logs with theSensitiveParameter
attribute #315doctrine/orm
dependency inrequire-dev
. DoesORM
3 || 4 affect bundle internals outside of testsdoctrine/persistence
how does this affect bundle outside of testsDependencyInjection
,Resources/config/verify_email_services.xml
, &VerifyEmailBundle::class
align with latest & greatest Symfony Bundle best practices - use new bundle structure #312@final
,@internal
where appropriate - make classes final #31610
/11
, at the very least ensure test suite is compatible w/ 10/11 where possible..php-cs-fixer.dist.php
as requiredphpunit.xml.dist
as requiredMakerBundle
, specifically,make:reset-password
where applicable to prefer2.x
usage2.x
or1.x
as required.baseline
symfony/clock
componentREADME.md
with bundle andmake:reset-password
The text was updated successfully, but these errors were encountered: