Estado de parcheo

Todos los parches tendrían un enlace de defecto ascendente o comentario

Todos los parches en los archivos de especificaciones de Fedora DEBERÍAN incluir un comentario sobre su estado original. Al crear un parche, se recomienda registrarlo en un sistema de seguimiento de errores original e incluir un enlace en el comentario sobre el parche. Por ejemplo:

# https://bugzilla.gnome.org/show_bug.cgi?id=12345
Parche: gnome-panel-fix-frobnicator.patch

Lo anterior es perfectamente aceptable; pero si lo prefiere, puede ser útil un comentario breve sobre lo que hace el parche mencionado anteriormente:

# No se bloquee con el subprograma Frobnicator
# https://bugzilla.gnome.org/show_bug.cgi?id=12345
Patch: gnome-panel-fix-frobnicator.patch

Sending patches upstream and adding this comment will help ensure that Fedora is acting as a good FLOSS citizen (see Staying Close to Upstream Projects). It will help others (and even you) down the line in package maintenance by knowing what patches are likely to appear in a new upstream release.

If upstream doesn’t have a bug tracker

You can indicate that you have sent the patch upstream and any known status:

# Sent upstream via email 20080407
Patch: foobar-fix-the-bar.patch

# Upstream has applied this in SVN trunk
Patch: foobar-fix-the-baz.patch

Fedora-specific (or rejected upstream) patches

It may be that some patches truly are Fedora-specific; in that case, say so:

# This patch is temporary until we land the long term System.loadLibrary fix in OpenJDK
Patch: jna-jni-path.patch

Why upstream?

Refer Staying Close to Upstream Projects

Want to help? Learn how to contribute to Fedora Docs ›