[META] Roadmap for a stable 2.0 release

I'll be attending Drupalcon Lille, anyone interested to work on getting this module to beta during the conference?

I'll be working on Localize ( 📌 [META] Localize server 3.0.x roadmap Active ). I'll be happy to pass by but alas I won't be able to work on an actual issue.

I'll be at Lille, not sure how much time I'll have on coding work though. But I'd be interested in chatting to maintainers about ✨ Define entity types programmatically Active .

nice thanks @FMB and good luck working on the localize server!

I want to move this project's status to beta since some sites already use the module and some projects require a more stable version of contrib. We are already quite far, but looking at the list of issues in this ticket, a could still take quite some time, which might prevent projects from using this module. I know there are some rough edges, but most user can use the basic functionality and others can extend and use their custom storage client.

Please comment otherwise I will proceed to mark this project beta 1

We have a first beta! Still a lot to improve but we are getting there :)

Adding ✨ Better support for query filtering and data saving Active to the list as it's something important if not mandatory for a release. Currently, no filtering occurs on REST clients for other operators than '=' and no warning message is provided.

Also adding 🐛 Multiple fixes for REST, Wiki and JsonAPI storage clients Needs work as it would solve many issues on REST clients, including ✨ Storage clients shouldn't be required to provide a response decoder factory Active currently still in the list.

Removed #3108827: Add return type hinting to all code → , 🐛 Multiple fixes for REST, Wiki and JsonAPI storage clients Needs work , ✨ Storage clients shouldn't be required to provide a response decoder factory Active and ✨ Better support for query filtering and data saving Active from list as they are now handled by v3.0.

Looks like we're targetting 3.0 now

Let's keep this meta issue for the 2.0 version and create another one for the 3.0.

I noticed some fixes being merged to the 3.0 only, I think they should also go to the 2.0 since that is the published stable. We need to keep the differences as small as possible to provide a smaller upgrade path and still benefit from the enhancements.

Agreed. I plan to create a separate roadmap for v3 and update the summary of this v2 roadmap to remove v3-related stuff from here.