This document describes an upstream fix tracking (UFT) workflow. It lists the stable branches and development branches of various open source projects. The workflow takes the 6.1.x branch as an example, explaining the process of reading commits between releases and the master branch, filtering them based on keywords and blacklists, and sending the results to a Slack channel. It also provides some tasks for future improvement, such as adding hyperlinks to commits, supporting different repositories, and separating CVEs from fixes.

1. digitalocean.com
Uptream-fixes-tracking
Liang Yan
Virt - KVP – Infra::Eng
https://github.com/liayan/uft
https://github.com/liayan/uft
https://github.com/liayan/uft
https://www.linkedin.co
Sharkahack 07/29/2022

2. Upstream git workflow
4.2 5.0 5.1 5.2 6.0 6.1 6.2 7.0 7.1.50
4.2.1
4.2.x
6.1.1
6.1.x
Stable branches:
6.1.1/4.1.1 All the patches are from the master branch
DO branches: Some of the patches are from the master branch
6.1.x/4.1.x Some of the patches are from us
master
https://github.com/liayan/uft
QEMU

3. Uft workflow
4.2 5.0 5.1 5.2 6.0 6.1 6.2 7.0 7.1.50
4.2.1
4.2.x
6.1.1
6.1.x
Take 6.1.x as example
master
1. Read commits between 6.1.0 and 6.1.1
2. Read commits between 6.1.x and 6.1.0 (extra script)
3. Read commits from blacklist file
4. Scan commits between 6.1.0 and master, choose the commits with pattern keywords
5. Filter with blacklist keyword and all commits from step 1-3
6. Send to slack channel: uft-lists
https://github.com/liayan/uft

4. 4
Todo
Add hyperlinkto each commit in slack
Python script for different
repos(kernel/libvirt/qemu)
Separate CVE from git-fixes
Add "cache" function
Search based on files
Re-write in golang?