]> git.ipfire.org Git - thirdparty/patchwork.git/commit
parser: Don't group patches with different versions in a series
authorStephen Finucane <stephen@that.guru>
Wed, 4 Mar 2020 15:48:56 +0000 (15:48 +0000)
committerStephen Finucane <stephen@that.guru>
Wed, 11 Mar 2020 10:10:50 +0000 (10:10 +0000)
commitd6ee204ef516643e62bcf27692dddf83e1042f5f
treeacef20aa0203775706507bf1de4779b3da7c9fef
parentb8a1673e356f2ad49f83eff82262b8d3c066f2fd
parser: Don't group patches with different versions in a series

As noted in #340 [1], if a patch from a series is dropped or
miscategorised, patches from a later revision of that series can end up
included in the earlier series rather than in their own series. This was
actually intentional as part of the fix for #105 [2]. However,
completely ignoring this information can be problematic. Refine things
by checking for versions and, if they don't match, using timeboxing to
try guess if they should be kept together. This would resolve the issue
seen in #340 while preventing a regression for #105.

[1] https://github.com/getpatchwork/patchwork/issues/340
[1] https://github.com/getpatchwork/patchwork/issues/105

Signed-off-by: Stephen Finucane <stephen@that.guru>
Tested-by: Ali Alnubani <alialnu@mellanox.com>
Related: #340
Related: #105
patchwork/parser.py
patchwork/tests/series/bugs-mixed-versions.mbox [new file with mode: 0644]
patchwork/tests/test_series.py
releasenotes/notes/issue-340-45deefed937b2090.yaml [new file with mode: 0644]