From Fedora Project Wiki

(use deprecate instead of retired)
(Move policy material to separate page, link there)
(35 intermediate revisions by 13 users not shown)
Line 1: Line 1:
== About Orphan and Retired (Deprecated) Packages ==
{{autolang|base=yes}}


When Fedora maintainers do not want or are not able to maintain a package any
This page contains instructions for working with orphan packages as specified in [[Policy for Orphan and Retired Packages]].
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.
 
Orphaned packages remain in the distribution and are the responsibility of the collective packaging community to maintain.
 
Retired packages are removed from the release. (They remain in prior releases.)
 
{{admon/warning|Retiring packages|Orphan packages will re retired if they remain orphaned. This is normally done shortly before branching for a new release.}}
 
{{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 ==
== Orphaning Procedure ==


# Announce on [https://lists.fedoraproject.org/mailman/listinfo/devel devel] which package you want to orphan.
# If the package has co-maintainers, contact them to ask whether one of them wants to take over ownership of the package. This step is optional. If no co-maintainer can be found to take over the package, the package should be given to the "orphan" user.<BR><BR>The current list of maintainers can be found in the "Users & Groups" tab of the setting for the package repo. The URL will look something like this — https://src.fedoraproject.org/rpms/PACKAGE_NAME/settings.
# Log into the [https://admin.fedoraproject.org/pkgdb/users/packages/ Package Database] and select the package you want to orphan.
# After the first step is finished, go again to the settings tab for your package's Pagure repository. Navigate down to the ''Give Project'' section and "give" the project to the new maintainer or the "orphan" user (in case no new maintainer was selected).
# Press the "Release Ownership" button for each active branch that you want to orphan.
# For completeness, under the ''Users and Groups'' section, remove yourself from the list as well.
# Also reset your watch status if you do not want to be CC'ed on new package bugs.
# If the package was given to the "orphan" user, announce on [https://lists.fedoraproject.org/mailman/listinfo/devel devel] which package you orphaned, so that others have a chance to take over as maintainer.
# Reassign the package's tickets to the orphan user, extras-orphan@fedoraproject.org.


== Claiming Ownership of an Orphaned Package Procedure ==
== Claiming Ownership of an Orphaned Package ==


# Check why the package was orphaned by looking for the email to [https://lists.fedoraproject.org/mailman/listinfo/devel devel].
# Check why the package was orphaned by looking for the email to [https://lists.fedoraproject.org/mailman/listinfo/devel devel].
# Announce on [https://lists.fedoraproject.org/mailman/listinfo/devel devel] which packages you would like to become the owner of.
# Announce on [https://lists.fedoraproject.org/mailman/listinfo/devel devel] which packages you want to take over.
# Log into the [https://admin.fedoraproject.org/pkgdb/users/packages/ Package Database] and select the package you want to become the owner of.
# Log in to [https://src.fedoraproject.org/ src.fedoraproject.org]. On the page with the orphaned package, click the '''✋ Take''' button in the left column. (If the option doesn't work for you, [https://pagure.io/releng/new_issue?template=package_unorphan&title=Unorphan%20%3Cpkgname%3E submit a ticket to the Release Engineering team], stating which package you want to claim and that this option didn't work.)
# Press the "Take Ownership" button for each active branch that you want to maintain.
# Reassign and claim all open bug reports for the package in Bugzilla.
# 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 ==
== Claiming Ownership of a Retired Package ==
Line 40: Line 28:
The process is a bit different from unorphaning a package
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 [https://lists.fedoraproject.org/mailman/listinfo/devel devel mailing list] or emailing the former maintainer. You can also check dead.package in the SCM (url like: [https://pkgs.fedoraproject.org/cgit/system-config-network.git/tree/dead.package https://pkgs.fedoraproject.org/cgit/'''package_name_here'''.git/tree/dead.package])
# See if you can figure out why the package was retired including searching for information about orphaned packages on [https://lists.fedoraproject.org/mailman/listinfo/devel devel mailing list] or emailing the former maintainer. You can also check dead.package in the SCM (url like: [https://src.fedoraproject.org/rpms/system-config-network/blob/rawhide/f/dead.package https://src.fedoraproject.org/rpms/'''package_name_here'''/blob/rawhide/f/dead.package])
# Announce on [https://lists.fedoraproject.org/mailman/listinfo/devel devel]  which packages you would like to become the owner of.
# Announce on [https://lists.fedoraproject.org/mailman/listinfo/devel devel]  which packages you would like to become the owner of.
# Retired packages require 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.
# Retired Fedora packages (rawhide branch retired) require a re-review if they are retired for more than eight 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 rereview, in the new rereview ticket (or existing one if the rereview is not required per the previous clause) to assign ownership to you.
# Request unretirement by filing a [https://pagure.io/releng/new_issue?template=package_unretirement&title=Unretire%20%3Cpkgname%3E releng ticket]. Specify all branches that need to be un-retired (inlcuding "rawhide" for Rawhide, unless it is for EPEL only) and include the link to re-review. In this ticket, request that the [[ReleaseEngineering|Release Engineering team]] unblock the package for the releases that the package should be un-retired for. In this request, clearly specify which branches should be unblocked.
# When the  SCM admin assigns the package to you it should unretire the package as well.  If the package status still says "Deprecated" or "Orphaned" instead of "Approved", you could have encountered a bug.  Please open a ticket on https://fedorahosted.org/fedora-infrastructure/ and assign it to "toshio" or contact toshio via irc:  abadger1999, or one of the mailing lists ([https://lists.fedoraproject.org/mailman/listinfo/infrastructure infrastructure list] or [https://lists.fedoraproject.org/mailman/listinfo/devel devel list])
# Restore the contents in GIT and prepare a new build and update (if necessary).
# Request that [[ReleaseEngineering|Release Engineering team]] unblock the package for the current release, via their [https://fedorahosted.org/rel-eng/newticket trac instance]. In this request, please post a link to the completed re-review.


== Lists of Orphan and Retired Packages ==
== Lists of Orphan and Retired Packages ==


* Currently [https://admin.fedoraproject.org/pkgdb/acls/orphans orphan packages] (also contains some deprecated packages).
* [https://src.fedoraproject.org/user/orphan A list of currently orphaned and/or retired packages]
* [[Deprecated packages]]  (not up to date, a complete list is currently not publicly available).
 
{{Anchor|core}}


[[Category:Package Maintainers]] [[Category:Policy]]
[[Category:Package Maintainers]]

Revision as of 11:46, 14 June 2021

This page contains instructions for working with orphan packages as specified in Policy for Orphan and Retired Packages.

Orphaning Procedure

  1. If the package has co-maintainers, contact them to ask whether one of them wants to take over ownership of the package. This step is optional. If no co-maintainer can be found to take over the package, the package should be given to the "orphan" user.

    The current list of maintainers can be found in the "Users & Groups" tab of the setting for the package repo. The URL will look something like this — https://src.fedoraproject.org/rpms/PACKAGE_NAME/settings.
  2. After the first step is finished, go again to the settings tab for your package's Pagure repository. Navigate down to the Give Project section and "give" the project to the new maintainer or the "orphan" user (in case no new maintainer was selected).
  3. For completeness, under the Users and Groups section, remove yourself from the list as well.
  4. Also reset your watch status if you do not want to be CC'ed on new package bugs.
  5. If the package was given to the "orphan" user, announce on devel which package you orphaned, so that others have a chance to take over as maintainer.
  6. Reassign the package's tickets to the orphan user, extras-orphan@fedoraproject.org.

Claiming Ownership of an Orphaned Package

  1. Check why the package was orphaned by looking for the email to devel.
  2. Announce on devel which packages you want to take over.
  3. Log in to src.fedoraproject.org. On the page with the orphaned package, click the ✋ Take button in the left column. (If the option doesn't work for you, submit a ticket to the Release Engineering team, stating which package you want to claim and that this option didn't work.)
  4. Reassign and claim all open bug reports for the package in Bugzilla.

Claiming Ownership of a Retired Package

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

  1. 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: https://src.fedoraproject.org/rpms/package_name_here/blob/rawhide/f/dead.package)
  2. Announce on devel which packages you would like to become the owner of.
  3. Retired Fedora packages (rawhide branch retired) require a re-review if they are retired for more than eight 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 the package review process for more information. To unretire a EPEL branch if the package is still in Fedora, no re-review is required.
  4. Request unretirement by filing a releng ticket. Specify all branches that need to be un-retired (inlcuding "rawhide" for Rawhide, unless it is for EPEL only) and include the link to re-review. In this ticket, request that the Release Engineering team unblock the package for the releases that the package should be un-retired for. In this request, clearly specify which branches should be unblocked.
  5. Restore the contents in GIT and prepare a new build and update (if necessary).

Lists of Orphan and Retired Packages