Roadmap for the 3.x branch

Done already:

- add an object based API to connections so you can just say $my_connection->callMethod('foo').
- clean up the admin UI for adding and editing connections.

On the way:

- add a page to test a connection, similar to what's in UpRPC and Content Distribution. Troubleshooting a services connection drives me mad and this sort of thing is a lifesaver!

Todo, anyone feel free to pick up the ball:
- fix Flickr client to work with the OO system
- move the code for making a connection add/edit form to the class
- refactor the OO code
- potentially rip out the static class code, or at least look at why it's needed
- rework the admin UI for resources
- rethink the whole system of specifying particular methods in clients and only one method per resource -- I'm low on use cases here, but as I'm not using resources at all it's very low priority

I think most of the above has been done, or has issues filed. Closing.

Actually, I'm going to reopen this as a roadmap...

Here's what I'm planning on doing, in rough order:

- add support for connections to Services 7.x-3.x: #1113136: support for Services 3.x. I don't think 6.x-3.x is worth the effort as there's already one way to connect to D6 services.
- reintroduce resources Mk2: #1038690: client resources Mk2.
- branch for D7.

Changes for D7 should be fairly minimal: mainly changes to FormAPI. I could do that now, but then the other changes above would have to be done on two branches at once which is a bit of a faff.

For a 3.0 release, I'd like:

#1915020: move handling of passwords to main module
#1143130: add delete button to connection & resource edit forms
#1858134: exporting a connection or resource should add the providing module as a dependency