On Thu, 28 Jan 2016 16:52:32 -0000
"John Florian" <jflorian(a)fedoraproject.org> wrote:
Oh, now my light bulb has a glow, dim it may be but it's not
utter
darkness any more. Tags in general in Koji are hard to understand
since they can take on so many uses.
Let's start from scratch. Here's what I am hoping to accomplish:
All builds initially are dumped into fN-candidates. These get mashed
into a repo, but I rarely use it -- it's mostly proof the build can
succeed at all. (Though, I'm now becoming aware of scratch/test
builds from HEAD via Koji so perhaps fN-candidates is unnecessary.)
If I want to actually try a build out, I "promote" it by untagging
from fN-candidates and tagging it with fN-testing. If functional
testing proves it good, then I'll promote again by untagging from
fn-testing and tagging with fN-released.
yes, that's quite common workflow
In the Fedora Project sense, I don't have any distinction
between
"base" and "updates". They're effectively squashed into my
fN-released as we've no need for anything but the newest functionally
tested version.
So, if IUYC, I should have my fN-build inherit from fN-released. Am
I correct?
yes
Will I be able to change my inheritance hierarchy for f21 & f22
or
will I have to wait and change my model once I start supporting f23?
with "koji edit-tag-inheritance" you can change it at any time
Dan