Maintenance of arbitrary branches of orphaned package

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Suppose I am main admin of a package which I would like to orphan in
release branches, but keep maintaining the package in arbitrary [1]
branches, which are used for building modules.  Would this considered
as a valid approach?

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
   orphan.
2. Set orphan as main admin and demote myself to just admin.

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.

[1] https://fedoraproject.org/wiki/Changes/ArbitraryBranching

-- 
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux