Is there any general roadmap or release schedule for Services 3? Specifically for Drupal 6, but also Drupal 7. Are we talking weeks, months, or a year before a production release?
I'd love to use Services 3 for the project and avoid recreating the wheel as so many have done, but more importantly I need stable code to support an api that will receive considerable public attention on launch. Yes, I know I can contribute but I'm still reliant on the Services team for the releases and the client of course has deadlines. Our goal is to build an uber-node module that provides a node resource on steroids. It would support querying by almost any imaginable node field, including cck fields, limits, pagination, workflow and og permissions, customizable cck field output and display (think 'display' tab for content types) etc. The uber-node module would then be contributed back to the community. So building on top of Services makes all the sense in the world if there's a stable release in the pipeline.
Regardless of what we use, you guys have done some great work, so thanks!
Comments
We're in RC-stage so we won't
We're in RC-stage so we won't release any changes that makes it impossible for you to keep your public API running (unless we find any crazy security hole that means your API is unsecure by design).
We are currently working on getting the a first stable release out - we do however have a few issues blocking that. Of those one or two might unfortunately require some backend changes - but only backend changes and its nothing complex and will be outlined clearly in the changelogs of upcoming releases. Your API will still look the same for your consumers.
I see no reason for you not to use Services. If you can - keep an eye in the issue queue and if you see any change you don't like - then tell so and we will of course take it into consideration. Not breaking compatability is a high priority. If you feel anything is blocking your use right now then tell so and we will try to fix it right away. If you make patches it will get fixed even faster.
voxpelli
Great, thanks for the response voxpelli, much appreciated. Hearing that you won't be breaking API functionality unless there are security issues is reassuring. Your quick response also shows there are people still working hard on Services which is also reassuring.
Most of my team was already on board with Services, and I think this seals it. If we run into issues we will report and hopefully patch.