At $dayjob, we build our own distro derived from EL6. We build the some
additional packages we need (which I'm introducing in Fedora whenever
possible), and so we have our own Koji setup.
We'd like to use Bodhi to manage updates and coordinate their QA-ing,
similarly to how it's done in Fedora.
However, one major difference is that we don't have two release levels
but three: "testing", "updates" and "release".
The first two work just like they do in Fedora.
But our customers asked us for a "patch Tuesday" process, so by default
the "updates" repository is not enabled, they take packages only in
"release". And every month, we move packages from "updates" to
"release". (We do have an "out-of-cyle" process where updates can be
pushed before the next "patch Tuesday" if required)
Reading the code, it seems to me that Bodhi is making the assumption
that there are two release levels only, as Release objects have a
"testing_tag" and a "stable_tag" attributes. Am I understanding this
If I am, is there a desire to have Bodhi able to implement our model? (I
can work on the implementation)
Or is there just no way to do that with Bodhi and I should start working
on our own home-made solution?
Show replies by date