From Fedora Project Wiki

(Undo revision 433396 by Axelvvd (talk))
(Replaced content with "{{admon/warning |This page has been moved out of the wiki. The current version of this document is located at")
Tag: Replaced
(21 intermediate revisions by 11 users not shown)
Line 1: Line 1:
== About Orphan and Retired (Deprecated) Packages ==
{{admon/warning |This page has been moved out of the wiki. The current version of this document is located at update your bookmarks.}}
When Fedora maintainers do not want or are not able to maintain a package any
longer, they can orphan or [[How_to_remove_a_package_at_end_of_life|retire]] the
package. When they think that the package is still useful for Fedora, they
should orphan it. Then other maintainers that are interested in maintaining it,
can take ownership of this package. In case the package is no longer useful for
Fedora, e.g. because it was renamed, upstream does not exist anymore, then it
should be retired. But this is only possible for development releases such as Branched or Rawhide.
Orphaned packages remain in stable releases and are the responsibility of the collective packaging community to maintain.
{{admon/warning|Retiring packages|Orphan packages will be retired if they remain orphaned for six weeks.}}
{{admon/warning|When to orphan and retire your packages|We encourage maintainers considering orphaning their packages to do it as early in the development cycle as possible. Shortly after the prior release is branched is a good time.}}
== Orphaning Procedure ==
# Announce on [ devel] which package you want to orphan.
# Log into the [ Package Database] and select the package you want to orphan.
# Press the "- Orphan Package" button and select the branches you want to orphan.
== Claiming Ownership of an Orphaned Package Procedure ==
# Check why the package was orphaned by looking for the email to [ devel].
# Announce on [ devel] which packages you would like to become the owner of.
# Log into the [ Package Database]  and select the package you want to become the owner of.
# Press the "Take Ownership" button for each active branch that you want to maintain.
# Take over and join (or re-assign to you) open bug reports in bugzilla where package owner's attention is needed.
== Claiming Ownership of a Retired Package ==
{{admon/warning|Un-Retiring long-time retired packages|Packages that are retired for Rawhide for more than two weeks need to be reviewed again before they can be un-retired. This is also true for EPEL-only packages.}}
If you really want to maintain a retired package, you need to be aware that
if upstream is dead, fixing release critical bugs, etc becomes your
responsibility. This is to ensure the high quality and standards of packaging
remain for Fedora package collection. There may be additional issues with
retired packages. If possible, consult with the former maintainer for more information.
The process is a bit different from unorphaning a package
# See if you can figure out why the package was retired including searching for information about orphaned packages on [ devel mailing list] or emailing the former maintainer. You can also check dead.package in the SCM (url like: ['''package_name_here'''.git/tree/dead.package])
# Announce on [ devel]  which packages you would like to become the owner of.
# Retired Fedora packages (master/devel/rawhide branch retired) require a re-review if they are retired for more than two weeks or if there is no previous review of the package. Submit a review request (a new bugzilla ticket) and have the package approved by a reviewer as if it were new to Fedora. See [[Package Review Process|the package review process]] for more information. To unretire a EPEL branch if the package is still in Fedora, no re-review is required.
# Open a [[package SCM admin requests|package SCM admin request]] after the re-review, in the new re-review ticket (or existing one if the re-review is not required per the previous clause) to assign ownership to you. Specify all branches that need to be un-retired (inlcuding "devel" for Rawhide, unless it is for EPEL only)
# Request that the [[ReleaseEngineering|Release Engineering team]] unblock the package for the releases that the package should be un-retired for via their [ trac instance]. In this request, please post a link to the completed re-review and clearly specify which branches should be unblocked.
# Restore the contents in GIT and prepare a new build and update (if necessary)
== Lists of Orphan and Retired Packages ==
* Orphan packages: [ Rawhide/master], [ EPEL 5], [ EPEL 6], [ EPEL 7]
* [[Deprecated packages]]  (not up to date, a complete list is currently not publicly available).
== References ==
=== EPEL ===
[[Category:Package Maintainers]] [[Category:Policy]]

Latest revision as of 06:09, 7 September 2021

This page has been moved out of the wiki. The current version of this document is located at Please update your bookmarks.