Handling Backport Changesets

[Dalibor Topic]

Fwiw, JIRA entries for backports record a single Assignee. Quoting from
https://wiki.openjdk.java.net/display/general/JBS+Overview

"Backports are full issues, but only a few fields are expected to be set:

     fixVersion: indicates which specific release a backport is 
targeting or fixed in
     assignee: holds the engineer responsible for the backport"

So my suggestion would be to simply keep that information accurate in 
JIRA as your 'Backported-by' information, rather than adding a category 
of metadata to commits.

This has a couple of advantages. It's not possible to fix mistakes in 
commit metadata, for example, while it can be done easily in JIRA.

cheers,
dalibor topic

On 29.03.2019 16:00, Andrew John Hughes wrote:
> Just a heads up that I've filed:
> 
> https://bugs.openjdk.java.net/browse/JDK-8221692
> 
> to try and get backporting formally recognised in changesets, in the
> same way as Contributed-by.
> 
> Hopefully, this will resolve the confusion over who to credit for such
> changes.
> 
> Thanks,
> 

-- 
Oracle <http://www.oracle.com>
Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961>

ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | D-22761 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Nederland, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher

Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment