On Sun, 2018-04-15 at 02:58 +1000, Daniel Axtens wrote:
> TL;DR: I want to spin a new version of patchwork for OzLabs so they can
> do the migration that speeds up patch listing. I've pushed it to
> https://github.com/daxtens/patchwork again (forcibly).
> 
>  * Thanks to Veronika for the name Eolienne.
> 
>  * I have reworked the release notes to use reno. Thanks Stephen.
> 
>  * I thought it was simplest to move unreleased.rst to eolienne.rst.
>    This means the 2.1.0 release won't contain an incongrous file of
>    'unreleased' changes! It requires that commit 1 after the final tag
>    reintroduces unreleased.rst to collect the next lot of changes;
>    that seems fine to me.

reno is a little funny. It's used extensively in OpenStack but the
release notes are built separately from the main docs and not
versioned. As a result, this kind of thing doesn't tend to be an issue.
If we see anything funky here, let me know and I'll work on it.

>  * Again, I've pushed this to https://github.com/daxtens/patchwork as
>    I'm not sufficiently confident in my release-fu to push it to the
>    main repo just yet. This includes a tag, v2.1.0-rc1. Stephen,
>    absent any further thoughts I'll push it to the main repo in the
>    coming days.

Personally I'd rather wait on the two things you mentioned below. The
API changes in particular are extensive enough and I'd like people
testing these as soon as possible (e.g. RC1). After that though, I'm
good: things like the labels feature can definitely wait a while
longer.

>  * I know there are a few more bits and bobs we want in, but I think
>    they're all sufficiently small to do as an rc2. Off the top of my
>    head it's my still-soon-to-come return code thing, and Stephen's
>    API tweaks.
> 
>  * Stephen, I can't find an api version code except in docs/api.yaml,
>    which I will freely admit to not understanding. AFAICT it's some
>    sort of API definiton but I don't know how to edit it. Please help.

This is currently defined in 'patchwork/urls.py' (the
'include(api_patterns)' line). We added in this release so we're going
to need to add a note about this to the prelude. Something as simple as
the below should do the trick.

    The API version has been bumped to 1.1.

>  * Testing and general feedback would be appreciated. :)
> 
> Thanks all for your contributions to Patchwork!
> 
> Regards,
> Daniel
> 
> Daniel Axtens (2):
>   docs: Prepare for 2.1.0-rc1
>   Patchwork v2.1.0-rc1
> 
>  docs/index.rst                                       |  2 +-
>  docs/releases/eolienne.rst                           |  5 +++++
>  docs/releases/index.rst                              |  2 +-
>  docs/releases/unreleased.rst                         |  5 -----
>  patchwork/__init__.py                                |  2 +-
>  releasenotes/notes/prelude-2_1-9fb70d76c5c835d4.yaml | 18 ++++++++++++++++++
>  6 files changed, 26 insertions(+), 8 deletions(-)
>  create mode 100644 docs/releases/eolienne.rst
>  delete mode 100644 docs/releases/unreleased.rst
>  create mode 100644 releasenotes/notes/prelude-2_1-9fb70d76c5c835d4.yaml
> 

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

Reply via email to