Orphaned package that need new maintainers

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(About Orphan and Deprecated Packages)
m (fix typo)
(3 intermediate revisions by 2 users not shown)
Line 9: Line 9:
 
{{admon/warning|Deprecating packages|Orphan packages will become deprecated if they remain orphaned. This is normally done shortly before branching for a new release.}}
 
{{admon/warning|Deprecating packages|Orphan packages will become deprecated if they remain orphaned. This is normally done shortly before branching for a new release.}}
  
{{admon/warning|When to orphan and deprecate your packages|We encorage 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.}}
+
{{admon/warning|When to orphan and deprecate 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 ==
Line 29: Line 29:
 
If you really want to maintain a deprecated 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 deprecated 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 deprecated 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 deprecated packages. 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 deprecated 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/gitweb/?p=orphaned_package_name_here.git;a=blob;f=dead.package )
+
# See if you can figure out why the package was deprecated 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])
 
# 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.
# Deprecated packages require re-review. 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.
+
# Deprecated packages require re-review if they are deprecated 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.
# Open a [[package SCM admin requests|package SCM admin request]] after the rereview, in the new rereview ticket) to assign ownership to you.
+
# 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.
 
# When the cvsadmin assigns the package to you it should undeprecate 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])
 
# When the cvsadmin assigns the package to you it should undeprecate 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])
 
# 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.
 
# 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.

Revision as of 21:46, 26 November 2012

Contents

About Orphan and Deprecated Packages

When Fedora maintainers do not want or are not able to maintain a package any longer, they can orphan or deprecate 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 deprecated.

Orphaned packages remain in the distribution and are the responibility of the collective packaging community to maintain.

Deprecated packages are removed from the release. (They remain in prior releases.)

Warning (medium size).png
Deprecating packages
Orphan packages will become deprecated if they remain orphaned. This is normally done shortly before branching for a new release.
Warning (medium size).png
When to orphan and deprecate 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 "Release Ownership" button for each active branch that 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 Deprecated Package

If you really want to maintain a deprecated 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 deprecated packages. 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 deprecated 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://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. Deprecated packages require re-review if they are deprecated 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.
  4. Open a 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.
  5. When the cvsadmin assigns the package to you it should undeprecate 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 (infrastructure list or devel list)
  6. Request that Release Engineering team unblock the package for the current release, via their trac instance. In this request, please post a link to the completed re-review.

Lists of Orphan and Deprecated Packages

  • Currently orphan packages (also contains some deprecated packages).
  • Deprecated packages (not up to date, may not contain packages that are in the orphan package list, but are actually deprecated).