The next release train

[VincentLanglet]

Even if #1715 is not finished (some contributors are working on it) we may want to move on for other sonata packages.

• SonataFormExtensions v2
  • Resolve deprecated code: Deprecate passing array to addViolation form-extensions#359
  • Drop support for PHP 7.3
  • Drop support for PHP 7.4
  • Add rector
  • Drop support for Symfony 4 (and twig 2 ?)
  • Update docs: Update doc form-extensions#354
  • Add support on SonataAdmin
  • Upgrade date picker form-extensions#335
  • Release alpha
  • Cleanup older upgrade files
  • Create 3.x branch and configure on dev-kit
  • Release stable
• BlockBundle v5
  • Resolve deprecated code
  • Drop support for PHP 7.3
  • Drop support for PHP 7.4
  • Add rector: Add Rector configuration SonataBlockBundle#1057
  • Drop support for Symfony 4 (and some lowest version of dependencies ?): Drop older versions SonataBlockBundle#1060
  • Update docs
  • Add support on SonataAdmin
  • Wait for PageBundle v4 to be sure we don't need any change on BlockBundle 4.
  • Release alpha
  • Add upgrade file
  • Add everything on upgrade file
  • Cleanup older upgrade files
  • Create 6.x branch and configure on dev-kit
  • Release stable

The best would be to support all those new versions on SonataAdmin without the need for a new SonataAdmin major version.

Done:

• SonataDoctrineExtension v2
• Exporter v3
• SonataTwigExtension v2
• SonataIntl v3
• SonataPage v4

[VincentLanglet]

cc @dmaicher @jordisala1991, since you started working on it

[dmaicher]

Regarding BlockBundle: Do we plan any more (breaking) changes for 5.0? Or are we close to releasing it?

@VincentLanglet maybe we can create another release on 4.x? See sonata-project/SonataBlockBundle@4.12.0...4.x

[VincentLanglet]

Regarding BlockBundle: Do we plan any more (breaking) changes for 5.0? Or are we close to releasing it?

I think we're close to releasing it.
But I thought we could focus on extensions library before

[VincentLanglet]

We might start soon to release the alphas cc @jordisala1991 @dmaicher

[VincentLanglet]

After the merge of sonata-project/exporter#593 we're ready.

Do you think we need an alpha/beta releases for those bundle ?

Edit: there are some issues to solve

• Upgrade Datetime library form-extensions#320
• Make getObjectManager protected on BaseManager sonata-doctrine-extensions#324

[VincentLanglet]

Seems ready:

• https://master-7rqtwti-ptm4dx6rjpjko.eu-5.platformsh.site/next-release/doctrine-extensions/2.x
• https://master-7rqtwti-ptm4dx6rjpjko.eu-5.platformsh.site/next-release/exporter/3.x
• https://master-7rqtwti-ptm4dx6rjpjko.eu-5.platformsh.site/next-release/form-extensions/2.x
• https://master-7rqtwti-ptm4dx6rjpjko.eu-5.platformsh.site/next-release/twig-extensions/2.x
• https://master-7rqtwti-ptm4dx6rjpjko.eu-5.platformsh.site/next-release/block-bundle/5.x

Form-extensions is blocked by sonata-project/form-extensions#335, but for others it's seems ok to make an alpha. Do you agree @jordisala1991 @dmaicher @sonata-project/contributors or do you see any others blocking points ?

[dmaicher]

Yeah good for me 👍

[jordisala1991]

Yes, we can do an alpha release for all of them and wait for the form-extensions

[VincentLanglet]

Blockbundle has a dependency on form-extensions
https://github.com/sonata-project/SonataBlockBundle/blob/5.x/composer.json#L28

For others, there are
sonata-project/sonata-doctrine-extensions#425
sonata-project/exporter#598
sonata-project/twig-extensions#331

[VincentLanglet]

Should we release the stable version of exporter/twig-extension and doctrine-extensions @jordisala1991 @dmaicher ?

[jordisala1991]

Exporter should be ready too. And we might try to prepare SonataIntlBundle too.

[VincentLanglet]

Yes, I'm starting SonataIntlBundle with sonata-project/SonataIntlBundle#531

[VincentLanglet]

Should we go for the stable release of SonataIntl 3 https://github.com/sonata-project/SonataIntlBundle/releases ?

[dmaicher]

@VincentLanglet could we release BlockBundle v5? 🤔 This is waiting for a long time now

I would like to get rid of

sonata-project/cache          2.2.0              2.2.0              Cache library
Package sonata-project/cache is abandoned, you should avoid using it. No replacement was suggested.

I just tested on my biggest project and it works fine for me with composer req sonata-project/block-bundle "5.x-dev as 4.99".

We need to allow ^5.0 on SonataAdminBundle though

[VincentLanglet]

I thought it was better to wait for formExtension before because of
https://github.com/sonata-project/SonataBlockBundle/blob/4.x/composer.json#L30
but maybe not.

I just tested on my biggest project and it works fine for me with composer req sonata-project/block-bundle "5.x-dev as 4.99".
Can you also try with formExtension 2.x-dev as 1.99 ?

I'd like to confirm that:

• The current 2.x branch doesn't require new BC break on blockBundle
• The last point Upgrade date picker form-extensions#335 doesn't require a BC break on BlockBundle (ping @jordisala1991)

Then we can release BlockBundle 5.0 and add later in a minor the FormExtension 2.0 support.

[dmaicher]

@VincentLanglet also additionally with composer req sonata-project/form-extensions "2.x-dev as 1.99" all my tests are passing and did some random manual testing: everything works fine

[VincentLanglet]

Then we can release BlockBundle 5.0 and add later in a minor the FormExtension 2.0 support.

So we can consider this strategy then. I'll try to get a confirmation from jordi.
(And I won't have a lot of time before february.)

I assume can start with an alpha anyway.

[VincentLanglet]

I lost track, not sure we did an alpha for block bundle v5. (cc @jordisala1991)

Now sonata-project/form-extensions#427 is merged, we could do an alpha for both block and form bundle.

[jordisala1991]

Yes, we did not do an alpha for block bundle. It would be nice to do it. Also for form extensions (I only need to take a look at the twig thing for form extensions).

Do you have time to prepare the block bundle one?