As shown at https://www.happyassassin.net/nightlies.html, we haven't
had a successful compose for almost two weeks. AIUI this is mostly
worked out now, but it raises the question: who should be keeping track
of this and coordinating fixes? For the releases, the blocker bug
process basically handles this, so functionally the ownership ends up
with QA (and the various heroes of QA who then track down all the
problems). For rawhide, we don't have any such thing. Is it rel-eng? Is
it FESCo? Is it the FPgM? Is it QA after all?
I suspect that right now, the answer is kind of "It's all of us
together", which unfortunately practically speaking often comes down to
0.02% per person and rounds down to 0.
Or if the answer is: "Matthew, you are the FPL. It's you!" … then fine,
but I'm going to then have to find some way to turn around and
I was chatting with Kevin Fenzi and he suggested naming a release
manager for each release — someone who would keep track of stuff
starting at branch, and help coordinate things like this.
This would help with more than just Rawhide — I'm sure everyone
involved in the blocker bug process would be grateful for more help. At
least, if it was someone who isn't already deeply involved in that. I'm
thinking probably someone selected from FESCo — but it also could be a
way for people with the particular set of skills required here to get
involved in a way that's different from FESCo membership.
What do you think?
Fedora Project Leader
Good Morning Fedorans!
On Thursday, a new version of Bodhi was deployed that enabled Bodhi to
gate updates based on test results. You may notice a "Test Gating
Status" message in the right have side of the page.
One thing to know about this is that there is currently a confusing
issue where Bodhi will say that the tests have failed when the tests
haven't finished running. We are working on solving that issue, but
for now you can just wait a while and it should report the result once
all the tests have finished.
There are three tests that must pass in order for updates to go to stable:
0. dist.depcheck - to make sure the update's dependencies are available.
1. dist.abicheck - to make sure the update's ABI remains stable in a
given Fedora release.
2. AtomicCI pipeline - packages that are part of the Atomic Host *and* include
in their dist-git tests, must have these tests passed in the AtomicCI pipeline
This last requirement only concern packages that are in the Atomic Host while
the first two is enforced for all packages.
We are also working on another CI pipeline that will allow running tests stored
in dist-git for all packages without discrimination.
You are in control of these three tests. The first two can be fixed by
making changes in the spec file, and the latter test is controlled via
the tests in your repo.
Finally, if it turns out you need to push an update through despite of the test
results, you can do so using waiver-cli (dnf install waiverdb-cli). We are
working on integrating this into Bodhi itself, making this easier.
We have started a wiki page to store all of this information and that we will
keep up to date as improvements are done or for any frequent questions coming up:
Please accept my apology in the delay in writing this message. It should
have been sent last week when it was enabled, and it got lost.
Thanks for your attention,
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org