Re: Patchwork v2.0.0 Available
Hi all,
> We're delighted to announce the release of Patchwork v2.0.0 ("Dazzle"):
Awesome!
I'm planning to update patchwork.ozlabs.org this weekend, at around
Sunday, 1pm (Australia/Perth timezone - UTC-8). Consequently, patchwork
will be unavailable during the upgrade.
The total timeframe somewhat depends on how smoothly the upgrade goes,
but one hour would be a conservative estimate.
Cheers,
Jeremy
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
Patchwork v2.0.0 Available
We're delighted to announce the release of Patchwork v2.0.0 ("Dazzle"):
https://github.com/getpatchwork/patchwork/releases/tag/v2.0.0
This release has been cooking for over 18 months and brings some fantastic new
features for users of development-focussed mailing list. Feature highlights of
v2.0.0 include:
* A REST API, which will eventually replace the legacy XML-RPC API
* Support for patch series
* Support for cover letters
...and many others. You can see the full list of changes in the release notes
[1]. You can also refer to the documentation for this release [2].
This should be the last major version bump for some time and we would encourage
users to upgrade as soon as possible. The development roadmap for future 2.x
versions of Patchwork is still in flux, but it's expected that we'll further
refine the UI and new REST API, as well as implement more of the features that
you, the community, have been asking for. For more info, or to provide feedback
on this and future releases, be sure to subscribe to the mailing list [3].
Finally, it's simply wonderful to look back at the amount of effort and support
that people around the world have put into making this the most feature-packed,
stable and secure Patchwork release to date. A huge thank you to everyone who's
contributed patches, submitted bug reports and provided general feedback over
the past 18 months. Patchwork 2.0 could not have been achieved without you.
Happy patchworking!
---
Patchwork is a patch tracking system for community-based projects. It is
intended to make the patch management process easier for both the project's
contributors and maintainers, leaving time for the more important (and more
interesting) stuff. You can find out more on the Patchwork homepage [4], the
GitHub repo [5], or the docs [6].
[1]: https://patchwork.readthedocs.io/en/latest/releases/dazzle/
[2]: https://patchwork.readthedocs.io/en/v2.0.0/
[3]: https://lists.ozlabs.org/listinfo/patchwork
[4]: http://jk.ozlabs.org/projects/patchwork/
[5]: https://github.com/getpatchwork/patchwork
[6]: https://patchwork.readthedocs.org/
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
Re: [PATCH 2/2] tests: Add test for updating tag counts in patch comments
On Mon, 2017-08-21 at 00:40 +1000, Andrew Donnellan wrote: > We accidentally broke the updating of tag counts for tags in comments, and > we didn't notice for quite a while. > > Add a test for this. > > Signed-off-by: Andrew Donnellan I considered merging this into the first patch, but it's fine being separate. Reviewed-by: Stephen Finucane Stephen ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: [PATCH 1/2] models: Fix invocation of refresh_tag_counts() for Comments
On Tue, 2017-08-22 at 12:47 +1000, Andrew Donnellan wrote:
> On 21/08/17 00:40, Andrew Donnellan wrote:
> > In Comment.save() and Comment.delete(), we always call
> > Submission.refresh_tag_counts(), which is an empty stub, rather than
> > calling Patch.refresh_tag_counts() if the Submission is a Patch.
> >
> > As such, tag counts are never updated on incoming comments.
> >
> > Delete Submission.refresh_tag_counts(), as it's useless, and in
> > Comment.save()/delete(), invoke Patch.refresh_tag_counts() directly when
> > the submission is a Patch.
> >
> > Reported-by: David Demelier
> > Fixes: 86172ccc161b ("models: Split Patch into two models")
> > Closes-bug: #111 ("A/R/T not updated on comments")
> > Signed-off-by: Andrew Donnellan
>
> Stephen - is this the last bug that's blocking the release? Happy to
> look at any other remaining blockers.
>
> I've pushed this fix to py{2,3}.patchwork.dja.id.au.
Yup, this looks good to me.
Reviewed-by: Stephen Finucane
Stephen
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork 2.0 ready for takeoff? (redux)
On Wed, 2017-08-02 at 11:27 +0100, Stephen Finucane wrote: > On Wed, 2017-07-26 at 17:46 +1000, Andrew Donnellan wrote: > > On 11/07/17 09:10, Daniel Axtens wrote: > > > One last bug: > > > > > > https://lkml.org/lkml/2017/7/8/33 is being incorrectly parsed as > > > https://py3.patchwork.dja.id.au/project/netdev/list/?series=4681 > > > > > > It looks like the square brackets are confusing the parser some how. > > > > > > After we squash this I say we just ship it. > > > > How are we going now? > > I've been away on vacation for the last week (*a* the emails) and am away > again next week. I don't think releasing this then disappearing for a week is > a great idea, so I'm tempted to wait til I'm back fully. In any case, as > things stand, it looks like there's the issue from David Demelier pointed out > to resolve and that's it. If anyone fancies taking a look at it (he appears > to have done the debug), I'd be mighty appreciative. > > Stephen OK, I'm back and the bug has been resolved (thanks, Andrew!). With that done, it looks like we're _finally_ done for the 2.0 release. Hurrah! I'll kick the release machine into action tonight and we should have a fresh new 2.0 release rolling out the door by tomorrow :) Thanks for all the hard work, folks. Much appreciated as always. Stephen ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
