From 90b4f35ec71c36e0338be6309731907d0b496329 Mon Sep 17 00:00:00 2001 From: Jiri Konecny Date: Tue, 28 Nov 2023 12:10:42 +0100 Subject: [PATCH] Update documentation for RHEL contributions We don't use Bugzilla anymore for RHEL bugs. Bugzilla was migrated to JIRA. --- CONTRIBUTING.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 7a98ab39b1a5..e3486caaf12f 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -132,12 +132,12 @@ The first line should be a succinct description of what the commit does, startin Commits for RHEL Branches ^^^^^^^^^^^^^^^^^^^^^^^^^^ -If you are submitting a patch for any rhel-branch, the last line of your commit must identify the bugzilla bug id it fixes, using the ``Resolves`` or ``Related`` keyword, e.g.: -``Resolves: rhbz#111111`` +If you are submitting a patch for any rhel-branch, the last line of your commit must identify the `JIRA issue `_ id it fixes, using the ``Resolves`` or ``Related`` keyword, e.g.: +``Resolves: jira#RHEL-11111`` or -``Related: rhbz#1234567`` +``Related: jira#RHEL-12345`` Use ``Resolves`` if the patch fixes the core issue which caused the bug. Use ``Related`` if the patch fixes an ancillary issue that is related to, but might not actually fix the bug.