From Fedora Project Wiki

(→‎Orphaning Procedure: Update for current pkgdb)
m (→‎Claiming Ownership of a Retired Package: fix package SCM admin request destination page)
Line 42: Line 42:
# 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 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.
# 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)
# Open a [[PackageDB_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 [https://fedorahosted.org/rel-eng/newticket trac instance]. In this request, please post a link to the completed re-review and clearly specify which branches should be unblocked.
# Request that the [[ReleaseEngineering|Release Engineering team]] unblock the package for the releases that the package should be un-retired for via their [https://fedorahosted.org/rel-eng/newticket 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)
# Restore the contents in GIT and prepare a new build and update (if necessary)

Revision as of 09:36, 1 February 2016

About Orphan and Retired (Deprecated) Packages

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. 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.

Retiring packages
Orphan packages will be retired if they remain orphaned for six weeks.
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

  1. Announce on devel which package you want to orphan.
  2. Log into the Package Database and select the package you want to orphan.
  3. Press the "- Orphan Package" button and select the branches you want to orphan.

Claiming Ownership of an Orphaned Package Procedure

  1. Check why the package was orphaned by looking for the email to devel.
  2. Announce on devel which packages you would like to become the owner of.
  3. Log into the Package Database and select the package you want to become the owner of.
  4. Press the "Take Ownership" button for each active branch that you want to maintain.
  5. 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

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

  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: http://pkgs.fedoraproject.org/cgit/package_name_here.git/tree/dead.package)
  2. Announce on devel which packages you would like to become the owner of.
  3. 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 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. Open a 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)
  5. Request that the 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.
  6. Restore the contents in GIT and prepare a new build and update (if necessary)

Lists of Orphan and Retired Packages

References

EPEL

Retrieved from "https://fedoraproject.org/w/index.php?title=Orphaned_package_that_need_new_maintainers&oldid=433396"