[wp-meta] [Making WordPress.org] #7952: Incorrect committer attribution when using Release Confirmation

[Making WordPress.org]

#7952: Incorrect committer attribution when using Release Confirmation
------------------------------+--------------------
 Reporter:  jorgeatorres      |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 When using Release Confirmation, we've noticed that frequently the
 "Committer" column shows someone from the team that wasn't directly
 involved with the tagging of the new version.

 For example, for the WooCommerce plugin, we've noticed that RC has
 attributed the following releases as follows:

 - [https://plugins.trac.wordpress.org/browser/woocommerce/tags/9.6.0
 9.6.0] to `konamiman` and `jorgeatorres`. Actual committer:
 `jorgeatorres`.
 - [https://plugins.trac.wordpress.org/browser/woocommerce/tags/9.7.0/
 9.7.0] to `jorgeatorres`and `albarin`. Actual committer: `albarin`.
 - [https://plugins.trac.wordpress.org/browser/woocommerce/tags/9.7.1/
 9.7.1] to `albarin` and `jorgeatorres`. Actual committer: `jorgeatorres`.


 [https://plugins.trac.wordpress.org/browser/woocommerce/ SVN] clearly
 shows who the committer was when those tags were created.

 How is RC obtaining the list of committers? This might be related to the
 internal tools we use to publish WooCommerce, but based on the above it
 does seem like SVN has the correct information to deduce the committer.

 This doesn't impact our ability to submit releases and we haven't noticed
 any other issues with RC lately.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7952>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org