[dpdk-dev] DPDK patchwork upgrade
> Hi all, > > Patchwork is upgraded from a pre-0.9 version to 1.1.1: > http://dpdk.org/dev/patchwork > > This new version brings 2 new columns: > > - A/R/T for Acked-by/Reviewed-by/Tested-by counters. > Unfortunately it does not yet parse the cover letter of a series. It's coming: https://github.com/getpatchwork/patchwork/commit/36953b Along with a REST API, thankfully: https://github.com/getpatchwork/patchwork/commit/92b6e6a > - S/W/F for Success/Warning/Fail counters in tests. > It will help to integrate the reports of distributed CI from > http://dpdk.org/ml/archives/test-report/ > > If you have some concerns or comments about this new version, > please reply here. I'm sure Stephen Finucane (cc'ed) will be > interested by our feedbacks. Better yet, use the mailing list: patchwork at lists.ozlabs.org Stephen
[dpdk-dev] DPDK patchwork upgrade
> 2016-09-07 16:40, De Lara Guarch, Pablo: > > I am looking at it, and I see two issues: > > - There are some patches that have been acked, but I don't see that in > > patchwork > > (e.g. http://dpdk.org/dev/patchwork/patch/15381/) > > Yes the new columns are empty. > I guess they will be filled starting from now. > Stephen, could we re-parse old emails (from August/September) to fill > A/R/T without breaking the database? You sure can - use the 'retag' command [1]: ./manage.py retag I should probably have included that in the upgrade notes... Stephen [1] https://github.com/getpatchwork/patchwork/blob/stable/1.1/patchwork/management/commands/retag.py
[dpdk-dev] DPDK patchwork upgrade
> > You sure can - use the 'retag' command [1]: > > > > ? ? ./manage.py retag > > > > I should probably have included that in the upgrade notes... > > > > Stephen > > > > [1] > > https://github.com/getpatchwork/patchwork/blob/stable/1.1/patchwork/management/commands/> > > retag.py > > That is looks really good and should save a lot of time for > maintainer taking already validated patches. How hard is connection > between patchwork, mailing list tags and testing system? Is that > all inside patchwork or you wrote it specially for dpdk?? I would > really like to have the same thing for my projects. Not difficult at all, and improving all the time. dpdk.org uses upstream Patchwork, so I'd suggest looking at the documentation [1] for some advice of getting both developer and deployment versions configured. Alternatively, Andy Doan in Linaro is working on Patchwork and might be able to help you out some? Stephen [1] patchwork.readthedocs.io/en/latest/development/
