mbox series

[0/2] Add writeable 'bundles' API

Message ID 20190908223147.25789-1-stephen@that.guru
Headers show
Series Add writeable 'bundles' API | expand

Message

Stephen Finucane Sept. 8, 2019, 10:31 p.m. UTC 
Hopefully self-explanatory. This closes another gap with the web UI and
REST API.

Stephen Finucane (2):
  REST: Add 'has_version' helper
  REST: Allow creating, updating, deleting of bundles

 docs/api/schemas/latest/patchwork.yaml        | 170 +++++++++++++++-
 docs/api/schemas/patchwork.j2                 | 181 +++++++++++++++++-
 docs/api/schemas/v1.0/patchwork.yaml          |   5 +-
 docs/api/schemas/v1.1/patchwork.yaml          |   5 +-
 docs/api/schemas/v1.2/patchwork.yaml          | 170 +++++++++++++++-
 patchwork/api/base.py                         |  12 +-
 patchwork/api/bundle.py                       |  84 +++++++-
 patchwork/api/utils.py                        |  14 ++
 patchwork/models.py                           |  11 ++
 patchwork/tests/api/test_bundle.py            | 118 +++++++++++-
 patchwork/tests/api/utils.py                  |  16 +-
 ...pdate-bundle-via-api-2946d8c4e730d545.yaml |   4 +
 12 files changed, 754 insertions(+), 36 deletions(-)
 create mode 100644 patchwork/api/utils.py
 create mode 100644 releasenotes/notes/update-bundle-via-api-2946d8c4e730d545.yaml

Comments

Stephen Finucane Oct. 15, 2019, 12:58 p.m. UTC | #1 
On Sun, 2019-09-08 at 23:31 +0100, Stephen Finucane wrote:
> Hopefully self-explanatory. This closes another gap with the web UI and
> REST API.

Assuming no one disagrees, I'm going to merge this series before the
end of the week. It has tests and documentation, suggesting it's low
enough risk, and is the sole remaining blocker for v2.2.0.

Stephen
Daniel Axtens Oct. 15, 2019, 9:58 p.m. UTC | #2 
Stephen Finucane <stephen@that.guru> writes:

> On Sun, 2019-09-08 at 23:31 +0100, Stephen Finucane wrote:
>> Hopefully self-explanatory. This closes another gap with the web UI and
>> REST API.
>
> Assuming no one disagrees, I'm going to merge this series before the
> end of the week. It has tests and documentation, suggesting it's low
> enough risk, and is the sole remaining blocker for v2.2.0.

Oh, sorry, had meant to test it by now. Not sure I will be able to get
that done in time, so I will trust the tests.

Could we squeeze the DMARC fix into 2.2? (And probably the fix for
https://github.com/getpatchwork/patchwork/issues/318 as well.)

Apart from that I think I'm OK with what we've got so far. I had hoped
we could get the patch relations stuff in but without a new spin of the
series I guess it will have to wait.

Regards,
Daniel


>
> Stephen
>
> _______________________________________________
> Patchwork mailing list
> Patchwork@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/patchwork