RestWS needs an official stable release as part of the Drupal.org D7 Upgrade Initiative

I think pushing for a 2.0 release before Drupalcon is hard, but not impossible. The web service CRUD API has not really changed from the 1.x to 2.x branch transition and has proven stable on quite a few production sites. Only the JSON Read part is needed on drupal.org as substitute for entity_json, which works and we don't have currently any bugs filed against that.

We introduced a big fat querying feature during GSoC which has not been tested and adopted much. Currently there is a critical security issue regarding querying, which is a release blocker of course (#1717410: Security: Querying does not respect node access grants). There are some other minor bug reports regarding files, creating multiple field items with a PUT request etc., but that would neither be relevant for drupal.org nor would it be a release blocker.

I'm on vacation for a week now, so I'm assigning this to fago if you need any immediate action.

I'm not sure how stable 2.0 already is as I've not participated much in its development.

@Senpai: Would using the 1.0 branch now work for you? This has been in use for quite some time, so I'd have no problem with doing a stable release there. Differences between 1.x and 2.x should be rather minor except for new features that have been added in 2.x only, i.e. improved setting of entity references by URLs, UUID support and the new querying part.

So the only API change is the handling of the PUT/POST semantics as noted on the project page, what should be simple to change when necessary later on.

So if going with 1.0 now works for you, I'd suggest we do that.

For the initial d.o D7 launch, all we care about is rendering issue nodes as JSON (e.g. to get #112805: JSON menu callback for project issues working without porting the custom code that handles this in the live D6 site). So long as the 7.x-1.x branch of RestWS can handle that, we definitely do not need a 2.0 release and a 1.0 release would be fine.

Thanks!
-Derek

Yep, that works fine for 1.x as well. Thus, I've tagged the 1.0 release there. -> http://drupal.org/node/1724186

If some project related stuff is missing from the JSON-output, make sure you've hook_entity_property_info() (see here) from the entity API module implemented - all what's there (and so avialable via the wrapper) works with RestWS as well.

Thanks fago for tagging 1.0, didn't think of that! Totally suffices for drupal.org and we don't need to worry about 2.x for now.