Re: Patchwork v2.0.0 Available
David Miller writes: > From: Michael Ellerman > Date: Mon, 28 Aug 2017 20:12:49 +1000 > >> Jeremy Kerr writes: >> >>> Hi all, >>> Just an update: the database migration for v2.0.0 is taking a *long* time, so we'll be out for more than that one hour. I'll get things back up and running as soon as possible, but we're dependent on this migration completing first. >>> >>> OK, we're back up now. Please let me know if anything looks amiss. >> >> Thanks jk. >> >> The series support and the clickable patch ids are big time savers for >> me. :beers: > > Agreed. > > Why not take the series support a step further? Make it like a > virtual bundle, have the "download mbox" button and everything else > there as well. > > As it is designed now, I still have to create a dummy bundle just to > get that mbox file for applying the patches. > > You should be able to eliminate that step entirely. I should be able > to do everything I can do from a bundle page, from the series page. > > Once something like that is in place, I'll be using bundles very > infrequently. Because capturing a patch series was my primary use for > them. I think there exists a way to do this. Something like you ask (a series mbox) exists: http://patchwork.ozlabs.org/series//mbox For example, get all 7 patches of the linuxppc-dev 'Add RSS to DPAA 1.x Ethernet driver' series at: http://patchwork.ozlabs.org/series/21/mbox You can find the series url with any patch (for example, in the linked series, I clicked on the first patch at http://patchwork.ozlabs.org/patch/806240/ and in the 3 boxes in the righthand corner saw |diff|mbox|series| - the |series| box will show the URL). There's also a project for interacting with pw called git-pw (http://github.com/getpatchwork/git-pw) and it can be used to download and apply all the patches in a series. As an example: $ git pw \ --server http://patchwork.ozlabs.org/ \ --project netdev --username myusername \ --password mypassword \ series show 21 +++ | Property | Value | |+| | ID | 21 | | Date | 2017-08-27T13:13:36 | | Name | Add RSS to DPAA 1.x Ethernet driver | | Submitter | Madalin Bucur (madalin.bu...@nxp.com) | | Project| Linux PPC development | | Version| 4 | | Received | 7 of 7 | | Complete | True | | Cover | 806235 [v4,0/7] Add RSS to DPAA 1.x Ethernet driver | | Patches| 806240 [v4,1/7] fsl/fman: move struct fman to header file | || 806242 [v4,2/7] fsl/fman: enable FMan Keygen | || 806241 [v4,3/7] dpaa_eth: use multiple Rx frame queues | || 806243 [v4,4/7] dpaa_eth: enable Rx hashing control | || 806244 [v4,5/7] dpaa_eth: add NETIF_F_RXHASH | || 806245 [v4,6/7] Documentation: networking: add RSS information | || 806246 [v4,7/7] dpaa_eth: check allocation result | +++ $ git pw \ --server http://patchwork.ozlabs.org/ \ --project netdev --username myusername \ --password mypassword \ series apply 21 Applying: fsl/fman: move struct fman to header file Applying: fsl/fman: enable FMan Keygen Applying: dpaa_eth: use multiple Rx frame queues Applying: dpaa_eth: enable Rx hashing control Applying: dpaa_eth: add NETIF_F_RXHASH Applying: Documentation: networking: add RSS information Applying: dpaa_eth: check allocation result Hopefully I didn't misunderstand the question. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
From: Jeremy Kerr Date: Thu, 31 Aug 2017 10:38:40 +0800 > Hi Andrew, > >> Ticket on github, after mpe and paulus complained about it: >> https://github.com/getpatchwork/patchwork/issues/116 >> >> I'll try and take a look at it today - jk, if I get a fix to you do you >> mind applying it on ozlabs.org? > > Can do! Thank you, I got burnt by this quite badly today. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Hi Andrew, > Ticket on github, after mpe and paulus complained about it: > https://github.com/getpatchwork/patchwork/issues/116 > > I'll try and take a look at it today - jk, if I get a fix to you do you > mind applying it on ozlabs.org? Can do! Cheers, Jeremy ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
On 29/08/17 08:03, David Miller wrote: Something else I noticed that feels like a regression to me. In the "bundle" box dialogue, there use to be a set of buttons for adding patches to an existing bundle. But it only has an option to create a new bundle. Although it isn't very often that I had to add patches from the main project queue to an existing bundle, but it does happen, and it's critically necessary when it occurs. But even more importantly, I used the existing bundle list in that dialogue to see if I have already added a set of patches to a bundle or not. So seeing the list of existing bundles there is very important. I would like to see this "add to existing bundle" everywhere the bundle box dialogue exists. Ticket on github, after mpe and paulus complained about it: https://github.com/getpatchwork/patchwork/issues/116 I'll try and take a look at it today - jk, if I get a fix to you do you mind applying it on ozlabs.org? Thank you. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ozlabs.org_listinfo_patchwork&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=-pHOU8dm1U-U1crivyxKr_-xvZrIBB8YUqvA3el0Ee0&m=aHV9QJsmxD7kAqZCdTgsOolAKc8lPk7EsmvpyXbwRHc&s=A51SSqtGLCddDiwJxV4ZX_ZCFLW6o2ZzcI-lGU297us&e= -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia Limited ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
On Mon, 2017-08-28 at 09:36 -0700, David Miller wrote: > From: Michael Ellerman > Date: Mon, 28 Aug 2017 20:12:49 +1000 > > > Jeremy Kerr writes: > > > >> Hi all, > >> > >>> Just an update: the database migration for v2.0.0 is taking a *long* > >>> time, so we'll be out for more than that one hour. I'll get things > >>> back up and running as soon as possible, but we're dependent on this > >>> migration completing first. > >> > >> OK, we're back up now. Please let me know if anything looks amiss. > > > > Thanks jk. > > > > The series support and the clickable patch ids are big time savers for > > me. :beers: > > Agreed. > > Why not take the series support a step further? Make it like a > virtual bundle, have the "download mbox" button and everything else > there as well. We do actually have this functionality, though it's only partially exposed in the web UI at the moment. Click into any patch that has an associated series and look at the top right corner. There are three links: 'diff', 'mbox', and 'series'. The last of these will download the patch with all its (series) dependencies. We don't currently expose a way to download an entire series via the web UI so you'll simply have to find the last patch in the series and click into that. You can also do this via the REST API. The 'git-pw' tool allows you to download both a patch+dependencies and the entire series: git pw patch apply [--[no-]deps] [PATCH_ID] git pw series apply [SERIES_ID] We'll probably add a more detailed series view to the web UI in a future release. > As it is designed now, I still have to create a dummy bundle just to > get that mbox file for applying the patches. > > You should be able to eliminate that step entirely. I should be able > to do everything I can do from a bundle page, from the series page. > > Once something like that is in place, I'll be using bundles very > infrequently. Because capturing a patch series was my primary use for > them. Stephen ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Some more UI feedback. Those mbox/diff buttons being placed at the top-right of the screen for a patch view is really inconvenient. All of my muscle memory for per-patch transactions now must be completely reprogrammed :-/ On my full screen Chrome window, it's a considerably far swipe of my mouse from where all of the actual action is on the left side of the screen for a patch view. It's previous placement was better, as a link right before the actual Patch. I've said the reasoning before, it's because I should be reading all of the feedback in the patch view before deciding to download and apply the patch. So that's where I'll be scrolling to and where I need to mbox download button to be. Thanks. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Something else I noticed that feels like a regression to me. In the "bundle" box dialogue, there use to be a set of buttons for adding patches to an existing bundle. But it only has an option to create a new bundle. Although it isn't very often that I had to add patches from the main project queue to an existing bundle, but it does happen, and it's critically necessary when it occurs. But even more importantly, I used the existing bundle list in that dialogue to see if I have already added a set of patches to a bundle or not. So seeing the list of existing bundles there is very important. I would like to see this "add to existing bundle" everywhere the bundle box dialogue exists. Thank you. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
From: Aaron Conole Date: Mon, 28 Aug 2017 13:37:13 -0400 > You can find the series url with any patch (for example, in the linked > series, I clicked on the first patch at > http://patchwork.ozlabs.org/patch/806240/ and in the 3 boxes in the > righthand corner saw |diff|mbox|series| - the |series| box will show the > URL). If you can make that series mbox download box show up when I click on the series, it's exactly what I need. It's not very useful from the individual patch page, in fact a button to get to the series pseudo-bundle would be more useful, because I'm going to have to update the state of all of the patches in the series when I apply them right? So the most useful inteface for a series is: 1) Click in series link from patch list for a project, f.e. http://patchwork.ozlabs.org/project/netdev/list/?series=225 2) Have a the "series mbox" button there, use it to download mbox and use that to apply the patches to my git tree. 3) Select "all" Patches radio button, use that to update the state of all of the patches of the series in one go. This would be my ideal workflow. Thanks. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
From: Michael Ellerman Date: Mon, 28 Aug 2017 20:12:49 +1000 > Jeremy Kerr writes: > >> Hi all, >> >>> Just an update: the database migration for v2.0.0 is taking a *long* >>> time, so we'll be out for more than that one hour. I'll get things >>> back up and running as soon as possible, but we're dependent on this >>> migration completing first. >> >> OK, we're back up now. Please let me know if anything looks amiss. > > Thanks jk. > > The series support and the clickable patch ids are big time savers for > me. :beers: Agreed. Why not take the series support a step further? Make it like a virtual bundle, have the "download mbox" button and everything else there as well. As it is designed now, I still have to create a dummy bundle just to get that mbox file for applying the patches. You should be able to eliminate that step entirely. I should be able to do everything I can do from a bundle page, from the series page. Once something like that is in place, I'll be using bundles very infrequently. Because capturing a patch series was my primary use for them. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Jeremy Kerr writes: > Hi all, > >> Just an update: the database migration for v2.0.0 is taking a *long* >> time, so we'll be out for more than that one hour. I'll get things >> back up and running as soon as possible, but we're dependent on this >> migration completing first. > > OK, we're back up now. Please let me know if anything looks amiss. Thanks jk. The series support and the clickable patch ids are big time savers for me. :beers: cheers ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
On Sun, 2017-08-27 at 22:10 +0800, Jeremy Kerr wrote: > Hi Andrew, > > > I'm seeing a 500 immediately upon login at > > https://patchwork.ozlabs.org/user/... > > OK, sorted. Looks like the permissions scripts are quite out-of-date > with the changes to the db. Damn - I tried to keep these up-to-date, but I don't use them myself and clearly missed some. If you could send a patch with the required fixes, I'd could merge it to 'stable/2.0' and mitigate the issue for anyone else. Thanks, Stephen ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
From: Jeremy Kerr Date: Mon, 28 Aug 2017 08:51:56 +0800 > Hi David, > >> Please look into this soon, thank you. > > OK, sorted. Permissions problem with the patchwork_event table. Let me > know if anything else is breaking. Seems to work now, thanks for looking into it. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
David Miller writes: > From: David Miller > Date: Sun, 27 Aug 2017 09:48:58 -0700 (PDT) > >> From: Jeremy Kerr >> Date: Sun, 27 Aug 2017 19:37:11 +0800 >> >>> Hi all, >>> Just an update: the database migration for v2.0.0 is taking a *long* time, so we'll be out for more than that one hour. I'll get things back up and running as soon as possible, but we're dependent on this migration completing first. >>> >>> OK, we're back up now. Please let me know if anything looks amiss. >> >> Go to: >> >> http://patchwork.ozlabs.org/project/netdev/list/?series=25 >> >> Click the box to the left of "Patch" field so all patches get selected. >> >> Select state of "Under Review" and delegate "davem", click update. >> >> Get a page with just "Server Error (500)" >> >> Happens every time I try it. > > I cannot change the state of any patch, which means I can't get any > work done at all today. I am able to modify patch states under the linuxppc-dev project. So maybe it's something netdev specific (somehow) ? cheers ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Hi David, Please look into this soon, thank you. OK, sorted. Permissions problem with the patchwork_event table. Let me know if anything else is breaking. Daniel: I also seem to be getting zero (email) notification of server-side errors, I assume from the new LOGGING configuration in base.py :( Cheers, Jeremy ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
On 28/08/17 10:02, David Miller wrote: I cannot change the state of any patch, which means I can't get any work done at all today. I've tried to log out and log back in again, same problem. Now that jk has fixed user login, I can change the state of my patches fine. -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia Limited ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
From: David Miller Date: Sun, 27 Aug 2017 09:48:58 -0700 (PDT) > From: Jeremy Kerr > Date: Sun, 27 Aug 2017 19:37:11 +0800 > >> Hi all, >> >>> Just an update: the database migration for v2.0.0 is taking a *long* >>> time, so we'll be out for more than that one hour. I'll get things >>> back up and running as soon as possible, but we're dependent on this >>> migration completing first. >> >> OK, we're back up now. Please let me know if anything looks amiss. > > Go to: > > http://patchwork.ozlabs.org/project/netdev/list/?series=25 > > Click the box to the left of "Patch" field so all patches get selected. > > Select state of "Under Review" and delegate "davem", click update. > > Get a page with just "Server Error (500)" > > Happens every time I try it. I cannot change the state of any patch, which means I can't get any work done at all today. I've tried to log out and log back in again, same problem. Please look into this soon, thank you. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
ozlabs instance borked [was: Patchwork v2.0.0 Available]
Jeremy, All, On Sun, 2017-08-27 09:48:58 -0700 (PDT), David Miller spake thusly: > Go to: > http://patchwork.ozlabs.org/project/netdev/list/?series=25 > > Click the box to the left of "Patch" field so all patches get selected. > Select state of "Under Review" and delegate "davem", click update. > Get a page with just "Server Error (500)" > Happens every time I try it. Ditto here, I get http/500 while trying to change the state of any patch for the Buildroot project, when it was working with the version previously deployed at ozlabs: https://patchwork.ozlabs.org/project/buildroot/list/ Regards, Yann E. MORIN. -- .-..--.. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `.---: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL| v conspiracy. | '--^---^--^' ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
From: Jeremy Kerr Date: Sun, 27 Aug 2017 19:37:11 +0800 > Hi all, > >> Just an update: the database migration for v2.0.0 is taking a *long* >> time, so we'll be out for more than that one hour. I'll get things >> back up and running as soon as possible, but we're dependent on this >> migration completing first. > > OK, we're back up now. Please let me know if anything looks amiss. Go to: http://patchwork.ozlabs.org/project/netdev/list/?series=25 Click the box to the left of "Patch" field so all patches get selected. Select state of "Under Review" and delegate "davem", click update. Get a page with just "Server Error (500)" Happens every time I try it. ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Hi Andrew, I'm seeing a 500 immediately upon login at https://patchwork.ozlabs.org/user/... OK, sorted. Looks like the permissions scripts are quite out-of-date with the changes to the db. Cheers, Jeremy ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
On 27/08/17 21:37, Jeremy Kerr wrote: OK, we're back up now. Please let me know if anything looks amiss. I'm seeing a 500 immediately upon login at https://patchwork.ozlabs.org/user/... -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia Limited ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Hi all, Just an update: the database migration for v2.0.0 is taking a *long* time, so we'll be out for more than that one hour. I'll get things back up and running as soon as possible, but we're dependent on this migration completing first. OK, we're back up now. Please let me know if anything looks amiss. Cheers, Jeremy ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Hi all, The total timeframe somewhat depends on how smoothly the upgrade goes, but one hour would be a conservative estimate. Just an update: the database migration for v2.0.0 is taking a *long* time, so we'll be out for more than that one hour. I'll get things back up and running as soon as possible, but we're dependent on this migration completing first. Cheers, Jeremy ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
On Thu, 2017-08-24 at 13:12 +0200, David Demelier wrote:
> Le 2017-08-23 20:59, Stephen Finucane a écrit :
> > We're delighted to announce the release of Patchwork v2.0.0 ("Dazzle"):
> >
> > https://github.com/getpatchwork/patchwork/releases/tag/v2.0.0
> >
>
> Thank you very much!
>
> I've upgraded my alpha-0 to 2.0.0 with success.
>
> However, in the footer I still see "version 2.0.0.alpha-0". Was that
> change forgotten?
Darn, so it was. I assume you were deploying from tarball rather than Git? You
can fix this manually as necessary, and I will issue a point release later this
week to resolve this.
Thanks for the heads up!
Stephen
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork v2.0.0 Available
Le 2017-08-23 20:59, Stephen Finucane a écrit :
We're delighted to announce the release of Patchwork v2.0.0 ("Dazzle"):
https://github.com/getpatchwork/patchwork/releases/tag/v2.0.0
Thank you very much!
I've upgraded my alpha-0 to 2.0.0 with success.
However, in the footer I still see "version 2.0.0.alpha-0". Was that
change forgotten?
Regards
--
David Demelier
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork
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
