Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release train #1715

Closed
46 tasks done
core23 opened this issue Oct 10, 2021 · 10 comments
Closed
46 tasks done

Release train #1715

core23 opened this issue Oct 10, 2021 · 10 comments

Comments

@core23
Copy link
Member

core23 commented Oct 10, 2021

There are still some project that do not have a stable version which supports sonata admin 4 or symfony 5/6.

This is an ordered list with all open steps for our main projects.

  • Next major: SonataSeoBundle
    • Create pre-release
    • Update documentation
    • Create release
  • Next major: SonataClassificationBundle
    • Bump psalm/phpstan level
    • Bump php version
    • Remove deprecations
    • Create pre-release
    • Update documentation
    • Create release
  • Next major: SonataMediaBundle
    • Bump psalm/phpstan level
    • Bump php version
    • Remove deprecations
    • Create pre-release
    • Update documentation
    • Create release
  • Next major: SonataTranslationBundle
    • Add symfony 5/6 support
    • Bump psalm/phpstan level
    • Bump php version
    • Remove deprecations
    • Create pre-release
    • Update documentation
    • Create release
  • Next major: SonataUserBundle
    • Drop FOSUserBundle
    • Add symfony 5/6 support
    • Bump psalm/phpstan level
    • Bump php version
    • Remove deprecations
    • Create pre-release
    • Update documentation
    • Create release
  • Next major: SonataFormatterBundle
    • Depends on SonataMediaBundle v4 (needs admin v4 support)
    • Add symfony 5/6 support
    • Bump psalm/phpstan level
    • Bump php version
    • Remove deprecations
    • Add formatter plugins (e.g. CKEditor, Markdown, ...)
    • Change services declaration from xml to php
    • Create pre-release
    • Update documentation
    • Create release

Referencing issues:

Continues #216

@VincentLanglet
Copy link
Member

We should also take a final decision for SonataUserBundle and communicate about it sonata-project/SonataUserBundle#1419

@core23
Copy link
Member Author

core23 commented Oct 10, 2021

We should also take a final decision for SonataUserBundle and communicate about it sonata-project/SonataUserBundle#1419

Yes, but this is an other topic to me. The bundle mentioned above are the sonata core bundle which are used for among each other.

@VincentLanglet
Copy link
Member

Yes, but this is an other topic to me. The bundle mentioned above are the sonata core bundle which are used for among each other.

That's exactly why I talked about the UserBundle. I consider it as one of our main bundle so it's not off topic
It's currently used a lot more than SonataPageBundle or SonataClassificationBundle for instance.

@jordisala1991
Copy link
Member

Keeping the documentation updated imo is another point on the list for each bundle that we should not forget.

@core23
Copy link
Member Author

core23 commented Oct 21, 2021

Feel free to add missing points

@VincentLanglet
Copy link
Member

@core23 @jordisala1991 Did you have time to test SonataMedia and SonataClassification dev branches ?
What's missing for a stable release ?

@jordisala1991
Copy link
Member

I didnt had time, and we first need to release classification. IMO we should release it and if someone reports anything we can do the bugfixes...

@core23
Copy link
Member Author

core23 commented Dec 23, 2021

@core23 @jordisala1991 Did you have time to test SonataMedia and SonataClassification dev branches ?

Not yet. Maybe I can find some time next week.

@VincentLanglet
Copy link
Member

I didnt had time, and we first need to release classification. IMO we should release it and if someone reports anything we can do the bugfixes...

I agree. Let's release Classification then

@VincentLanglet
Copy link
Member

I moved page bundle to #2009 in order to have only one issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants