Hi,

I am currently working on the HAProxy update in all supported Ubuntu LTS
releases (18.04, 20.04 and 22.04), here is the process we are using to
update it in stable releases [1]. One of the requirements to make the
Ubuntu SRU (Stable Release Updates) team allow the update is to have the
CI results log of those minor releases in place. Right now, I am working
on 2.4.18, 2.0.29 and 1.8.30.

I see that the GitHub is used only for the development branch, so the
other repos for HAProxy LTS releases are tracked only in
git.haproxy.org. However, since those minor releases are not on GitHub
we cannot check for instance if all CI tests are passing, and this is
mandatory for Ubuntu stable updates. What I am doing is creating a fork
on GitHub, pulling the branches and tags from git.haproxy.org, and
pushing them to GitHub, so the GitHub Actions are triggered (TravisCI
requires a subscription to run tests so I am not doing that).

Would it be possible to keep those branches and tags on GitHub as well?
So we can more easily find associated CI test results.

[1] https://wiki.ubuntu.com/HAProxyUpdates

TIA!

-- 
Lucas Kanashiro


Reply via email to