Created on 6 February 2024, 11 months ago
Updated 15 February 2024, 10 months ago

Proposal roadmap

Quite a few things in flight here so wanted to make a roadmap to align on direction and delivery.

3.x

Drop support asap and prioritise deprecations and simple backports. Release 3.2.0 as the final minor release of 3.x.

- #3414395 Drush 12 support πŸ› Drush 12 compatibility Downport (backport)
- #3349968 Queue & Exchange name property πŸ› Unable to provide queue or exchange configuration when using dotted naming convention Downport (originally a backport, but i think we should prioritise deprecation)
- #3419132 ConnectionFactory deprecation πŸ“Œ Deprecate ConnectionFactory and ConnectionFactory::getConnection() Active (deprecation)

4.x

Focus on a stable 4.0.0 release.

- #3416008 Make conversion from json to php serialization easier πŸ“Œ Make conversion from json to php serialization easier when upgrading to 4.x Active
- #3416009 Allow serialization mode to be configured per queue. ✨ Allow serialization mode to be configured per queue. Active
- #3154693 Support exchange and queue different config for different rabbitmq servers ✨ Support exchange and queue different config for different rabbitmq servers Needs work

5.x

5.x-dev is currently just a branch of of 4.x at time of writing but is intended to be a major refactor. Currently proposed deprecations targeted at 3.x until the release of 3.2.0 after will be targeted at 4.x.

- #3419129 Refactor ConnectionFactory & ServiceProvider πŸ“Œ Major refactor of ConnectionFactory and RabbitmqServiceProvider Active

🌱 Plan
Status

Active

Version

3.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom zach.bimson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @zach.bimson
  • πŸ‡ΊπŸ‡ΈUnited States cmlara

    3.x

    Drop support asap and prioritise deprecations and simple backports. Release 3.2.0 as the final minor release of 3.x.

    We will want to keep 3.x support for at least a few months after 4.0.0 is released to allow a transition window. We can mark it 'not recommended ' as soon as the 4.0.0 release is out.

  • πŸ‡¬πŸ‡§United Kingdom zach.bimson

    Sorry I should have been clearer, I meant new feature development. Support absolutely agree!

Production build 0.71.5 2024