Research rebase vs. backport decision #226
Conversation
| - check past issues to see if the package is usually rebased, if the fixes are usually backported, | ||
| or a combination of both, and suggest a way to proceed based on that |
There was a problem hiding this comment.
this is an excellent point
| - perform the rebase anyway, do a scratch build and provide results of abidiff check | ||
| and output of reverse dependency tests |
There was a problem hiding this comment.
in theory, we could do both and let the maintainer decide
There was a problem hiding this comment.
uh, you suggest this below :)
There was a problem hiding this comment.
do you see a value in doing some of the checks beforehand, I assume some license change check, also the ABI/API, comparing the CVEs present in both versions?
There was a problem hiding this comment.
do you see a value in doing some of the checks beforehand, I assume some license change check, also the ABI/API, comparing the CVEs present in both versions?
You mean doing the checks on upstream sources? Sure, what would have some value, but the more downstream patches the less trustworthy it would be.
nforro
force-pushed
the
rebase_decision
branch
2 times, most recently
from
c9d3933 to
9f3c60f
Compare
Signed-off-by: Nikola Forró <[email protected]>
TomasTomecek
left a comment
TomasTomecek
left a comment
There was a problem hiding this comment.
Thanks, very nice writeup, let's merge
4 participants
No description provided.