Re: REST-API: Merging/Rebasing with Mercurial?

OK, I managed to convert the changes from the repo converted from git
to a patchset using mq and apply this to a fresh SF checkout. Then I
merged the branch and pushed the result.

To make a long story short:
- Roundup now has a REST API from the 2015 GSOC implemented by Chau
  Nguyen and mentored by Ezio Melotti
- I've made it work with python3, all tests pass with python2 and
  python3
- In the process I've merge two bug-fixes from the bugs.python.org
  branch.
- Also corrected some problems, notably did not allow to delete an
  entire class (I don't see a use-case there) and retire items on delete
  not *destroy* them. Not even the admin interface to roundup exposes
  the destroy method.
- Documentation is still missing, I'll write it
- I discovered an undocumented feature of the XMLRPC API in the process:
  There is an "action" method which takes the action as the first
  parameter and additional parameters for the action, e.g.
  srv.action  ('retire',  'issue1')
  I've added a 'restore' action to undo a retire.
- The REST API also exposes this action API via the patch method
- I made both, XMLRPC and REST configurable in config.ini, so you can
  turn the REST API off if you don't trust it yet. Admins may want to
  enable only one of the two interfaces or none for security or other
  reasons. By default both APIs are enabled.

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]