From Fedora Project Wiki

(Clarify that I rereview needs a new bz ticket)
(Move policy material to separate page, link there)
 
(51 intermediate revisions by 20 users not shown)
Line 1: Line 1:
== About Orphan and Retired Packages ==
+
{{autolang|base=yes}}
  
When Fedora maintainers do not want or are not able to maintain a package any longer, they can orphan or 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.
+
This page contains instructions for working with orphan packages as specified in [[Policy for Orphan and Retired Packages]].
  
 
== 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] and checking dead.package in the SCM (url like: https://pkgs.fedoraproject.org/gitweb/?p=orphaned_package_name_here.git;a=blob;f=dead.package ).
+
# 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.
 
 
 
{{admon/warning|Re-review required for older packages|If a package was last updated more than three months ago (running git log *.spec can show you this information), you will need to 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. There are a couple of small changes though, be sure to submit a 'update' request to the SCM, and before you will be able to run the final 'make build' commands you will need to file a ticket w/ release engineering to unblock your package https://fedorahosted.org/rel-eng/newticket}}
 
  
 
== Claiming Ownership of a Retired Package ==
 
== Claiming Ownership of a Retired Package ==
  
If you really want to maintain a retired package, you need to be aware that 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. Consult with the former maintainer for more information. The process is a bit different from unorphaning a 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
  
# 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
+
# 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.
## At the moment, most retired packages fall under the "orphaned for more than three months" rule so they need a rereview.
+
# 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]] (if applicable, after the rereview, in the rereview ticket) 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 cvsadmin assigns the package to you it should unretire the package as well. If the package status still says "Deprecated", "Retired", or "Orphaned" instead of "Approved", you could have encountered a bug. Please open a ticket on https://fedorahosted.org/fedora-infratructure/ 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).
  
 
== 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 retired packages).
+
* [https://src.fedoraproject.org/user/orphan A list of currently orphaned and/or retired packages]
* [[PackageMaintainers/RetiredPackages|  Retired packages (wiki)]]  (not up to date, may not contain packages that are in the orphan package list, but are actually retired).
 
 
 
{{Anchor|core}}
 
  
[[Category:Package Maintainers]] [[Category:Policy]]
+
[[Category:Package Maintainers]]

Latest 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