On Wed, Jan 19, 2011 at 9:16 PM, Mike McLean <[email protected]> wrote:
> Furthermore you will note that the > 'latest' build in a given tag is the one that was most recently tagged > there rather than the one with the greatest version-release. Uhm, that's interesting and probably not what I would expect. > While different folks use tags and inheritance differently, I would > generally consider such a situation to be incorrect tagging. Inheritance > is intended as a progression of sorts, so I don't think it makes sense > to tag an older build in a child tag unless you are deliberately overriding. Sure it is! The incorrect tagging happened just because I made wrong assumptions. Now that I know how it works I'll just prevent it from happening. > What I can see is adding a policy check that could be used in the tag > policy to prevent such masking builds from being tagged (though of > course admins can override tag policy with --force). This is what I was thinking to do. -- Alan Franzoni -- contact me at public@[mysurname].eu -- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
