----- Original Message ----- > From: "Daniel Axtens" <d...@axtens.net> > To: patchwork@lists.ozlabs.org > Sent: Thursday, April 5, 2018 7:02:59 PM > Subject: [PATCH 0/2] Patchwork 2.1.0-rc1: Extra Special OzLabs Edition > > 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 as I'm not sufficiently confident > in my release-fu to push it to the main repo just yet. Let me know if > it looks good. > > From the release notes: > ====== > > Patchwork 2.1.0 - the Extra Special OzLabs Edition > > The key part of this release is a major performance fix - > denormalising the project field into patch model so that counting a > project's patches doesn't require a JOIN. This requires a migration > and so isn't suitable for a stable backport. Event listing in the API > has also been sped up by refactoring the queries. > > This release also includes the feature development that had accured in > the mean time, as laid out below*, and numerous bug fixes. > > * not in this email, see the patches. > ==== > > Some other thoughts/notes: > > * 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 > rants from you I will push it to the real repo mid-next week > > * I know the patch counting isn't a full fix of everything that could > or should be denormalised, but it's an ongoing problem and I don't > want another 6 months of maintainer-guilt about the ongoing impact > it's having. > > * Normally releases are named after a fabric, but it's hard to find > good fabrics beginning with E, at least according to the wikipedia > list. I am very open to renaming/rewording stuff, hence the emails > with the patches! >
What about Eolienne [1] ? Another possibility might be elastane, but that IMHO doesn't sound very fancy. [1] https://en.wikipedia.org/wiki/Eolienne Veronika > * There's a decent chance I've missed a version number somewhere - > please check your favourite locations! > > * What else do we want in 2.1? I think at least the return code fix - > it needs a v3 from me. (I would have done that first but I really > wanted to get this out tonight/this morning for general awareness > and comment.) I'm happy to take any more fixes or small things, but > probably not big things. Feel free to post them and we can review > them and get them ready to merge as soon as we tag 2.1.0 though! > > * 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/conf.py | 4 ++-- > docs/index.rst | 1 + > docs/releases/extra-special-ozlabs-edition.rst | 33 > ++++++++++++++++++++++++++ > docs/releases/index.rst | 1 + > patchwork/__init__.py | 2 +- > 5 files changed, 38 insertions(+), 3 deletions(-) > create mode 100644 docs/releases/extra-special-ozlabs-edition.rst > > -- > 2.14.1 > > _______________________________________________ > Patchwork mailing list > Patchwork@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/patchwork > _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
