On 08/27/2018 04:24 PM, Mikolaj Izdebski wrote:
Suppose I am main admin of a package which I would like to orphan in
release branches, but keep maintaining the package in arbitrary 
branches, which are used for building modules. Would this considered
as a valid approach?
I would think we should support it, yes.
How should I handle orphaning the package in this case? I can think
of at least two possibilities:
1. Keep myself as admin and set bugzilla_contact for product Fedora to
2. Set orphan as main admin and demote myself to just admin.
Well, I would say 1 is better than 2, but also note that bugs may well
be misrouted here. I guess that they should be filed against the module,
but people might file them against the rpm component since thats what
they are used to, so having that be orphan with you watching it might be
We could also try and improve our scripts here and close the rpm version
to new bugs with a note to file on the module? that would take some
In case no one adopts orphaned package and it is retired by Release
Engineering, should commiters be still able to commit to non-retired
arbitrary branches? I assume yes, but I'd rather ask in advance.
I think yes... but not 100% sure.