tldr; patches.linaro.org will be upgraded tomorrow, Wednesday the 9th around 16:00UTC.
patches.l.o is being updated with a number of new improvements:
* We are no longer a fork of the patchwork project and can stay up-to-date with improvements from the project.
* Team memberships are now handled correctly. In the past moving to a new team meant we could either leave you in both teams and then show patch credits to both teams or remove you from the old team and have that team lose all contributions you made.
* Multiple emails fixed. In the past doing Linaro work under another email (say @kernel.org) didn't properly contribute to patch metrics. This has been fixed (assuming you add your additional email account(s) to patches.l.o).
* Performance - the new data layout is much more efficient resulting in faster page loads.
Does Rest API works now?
Plan is connect pwclient and Jenkins for testing all patches in mailing list. Did somebody already do that?
On 02/09/16 21:28, Andy Doan wrote:
tldr; patches.linaro.org will be upgraded tomorrow, Wednesday the 9th around 16sts:00UTC.
patches.l.o is being updated with a number of new improvements:
- We are no longer a fork of the patchwork project and can stay
up-to-date with improvements from the project.
Can we extend local patchwork table with one more field like test result?
Maxim.
- Team memberships are now handled correctly. In the past moving to a
new team meant we could either leave you in both teams and then show patch credits to both teams or remove you from the old team and have that team lose all contributions you made.
- Multiple emails fixed. In the past doing Linaro work under another
email (say @kernel.org) didn't properly contribute to patch metrics. This has been fixed (assuming you add your additional email account(s) to patches.l.o).
- Performance - the new data layout is much more efficient resulting
in faster page loads. _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
On 02/11/2016 03:09 AM, Maxim Uvarov wrote:
Does Rest API works now?
The Rest API for patchwork is a fork being maintained outside the official patchwork project. The original attempt to merge was rejected because it was extremely large and changed many other parts of patchwork along with it. I don't think it will be upstreamed (and thus used by us) until someone makes a targeted patch-set to support it.
Plan is connect pwclient and Jenkins for testing all patches in mailing list. Did somebody already do that?
On 02/09/16 21:28, Andy Doan wrote:
tldr; patches.linaro.org will be upgraded tomorrow, Wednesday the 9th around 16sts:00UTC.
patches.l.o is being updated with a number of new improvements:
- We are no longer a fork of the patchwork project and can stay
up-to-date with improvements from the project.
Can we extend local patchwork table with one more field like test result?
The table currently has a "S/W/F" column for Success/Warning/Failure. Would this be sufficient? If so, I can take a look into trying to enable it for you.
On Tuesday 09 February 2016 12:28:06 Andy Doan wrote:
tldr; patches.linaro.org will be upgraded tomorrow, Wednesday the 9th around 16:00UTC.
Hi Andy,
I just stumbled over some broken links when looking up old patches in the archive. Specifically, this link https://patches.linaro.org/57380/ was supposed to take me to an older patch I have to revisit, but I get a 404 error.
Is this expected? Any chance to redirect the old links to a static archive of the original contents?
Arnd
On 02/12/2016 03:07 PM, Arnd Bergmann wrote:
On Tuesday 09 February 2016 12:28:06 Andy Doan wrote:
tldr; patches.linaro.org will be upgraded tomorrow, Wednesday the 9th around 16:00UTC.
Hi Andy,
I just stumbled over some broken links when looking up old patches in the archive. Specifically, this link https://patches.linaro.org/57380/ was supposed to take me to an older patch I have to revisit, but I get a 404 error.
Is this expected? Any chance to redirect the old links to a static archive of the original contents?
It was unanticipated. I had taken a snapshot of the old server's DB on around Oct. 23, 2015, 2:48 p.m. At that point the new server and old server stopped producing the same patch ID for patches. So patches after 55493 differ between the servers. I didn't anticipate people bookmarking stuff.
I've just made a small hack to stop the immediate issues: the new patchwork server prefixes patch URLs with "patch/<patch id>". So I can intercept all requests to that. If its <= 55493 its safe for my new system to display it. If its > 55493, I can assume that's a link that happened during this transition and redirect to the old patches server. eg - your link will work how you described now.
That's what we have for now. If this is sufficiently annoying to people, I can try to re-run a DB migration from the old server to the new one.
-
Andy Doan -
Arnd Bergmann -
Maxim Uvarov