-
Type:
Enhancement
-
Status: New
-
Priority:
P4
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: infrastructure
-
Labels:None
-
Subcomponent:
-
CPU:generic
-
OS:generic
There is a quandary in backporting changes to earlier JDK versions as to who to credit the work to, particularly where significant new work is required for the change to apply to the older version.
Committing the change under the name of the backporter fails to credit the original author. This is particularly problematic where there is little change to the original (e.g. just path changes or fuzzing). On the other hand, using the name of the original author eradicates the backporter's role altogether.
I suggest we adopt an additional field in the commit message, along the same lines as the existing 'Contributed-by". That would also allow backporters to be credited who don't have commit rights.
e.g.
8189761: COMPANY_NAME, IMPLEMENTOR, BUNDLE_VENDOR, VENDOR, but no configure flag
Reviewed-by: erikj, dholmes, clanger
Backported-by: Andrew Hughes <gnu.andrew@redhat.com>
Committing the change under the name of the backporter fails to credit the original author. This is particularly problematic where there is little change to the original (e.g. just path changes or fuzzing). On the other hand, using the name of the original author eradicates the backporter's role altogether.
I suggest we adopt an additional field in the commit message, along the same lines as the existing 'Contributed-by". That would also allow backporters to be credited who don't have commit rights.
e.g.
8189761: COMPANY_NAME, IMPLEMENTOR, BUNDLE_VENDOR, VENDOR, but no configure flag
Reviewed-by: erikj, dholmes, clanger
Backported-by: Andrew Hughes <gnu.andrew@redhat.com>