Making WordPress.org

Opened 4 years ago

Closed 3 years ago

#5649 closed task (blessed) (fixed)

Gutenberg Props: WordPress 5.7

Reported by: desrosj's profile desrosj Owned by:
Milestone: Priority: normal
Component: Profiles Keywords:
Cc:

Description

Previously:

Similar to the tickets above, we need to capture those who received props in Gutenberg and then ensure they're included in the 5.7 Credits API.

Change History (5)

#1 @desrosj
4 years ago

Here is a Google Doc with the results so far: https://docs.google.com/spreadsheets/d/11pA2LM67fQ3q89ok-oMcGlzE1_vOJkPBMkn1tLGtWbI/edit?usp=sharing

Process followed to get here:

  • git shortlog -sen v9.2.0...v9.9.0 > 5-7-gutenprops.txt (diff comparison)
  • Manually merged in props for the beta and RC PRs backporting fixes.
  • git log --format=" %(trailers:key=Co-authored-by)" v9.2.0...v9.9.0 > coauthored.txt for a list of contributors mentioned in the Co-authored-by trailers.
  • Manually merged the co-authors into the GitHub tab.
  • Manually worked to link .org usernames to that sheet.
  • Ran the props parser for .org using the log produced by git log b73f9fc5f6bfa24621bca59c4b06b3b199dbb73f...f2ca1e00d8297ee2d3b6c3c012a2c86f493006d1 > commits.log (when trunk became 5.7 alpha to when it became 5.8 alpha).
  • Merged the two sheets and merged duplicates.

Rows with a .org username will turn green. So all white rows are missing .org names. The release squad is working to fill in the rest, but any help eliminating duplicates or finding .org names is appreciated!

Last edited 4 years ago by desrosj (previous) (diff)

#2 @dd32
4 years ago

Rows with a .org username will turn green. So all white rows are missing .org names.

I've filled in what I can on the Combined list, 7 left now.
I think I missed copying a few into the GitHub sheet though.

but any help eliminating duplicates

There's a few in there I think, I didn't do any attempt at fixing the

#3 @dd32
3 years ago

@desrosj was this completed..?

#4 follow-up: @desrosj
3 years ago

It was! Forgot to follow up. Looks like I can't close tickets as fixed, though.

#5 in reply to: ↑ 4 @dd32
3 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Replying to desrosj:

Looks like I can't close tickets as fixed, though.

Next time you will be able to!

Note: See TracTickets for help on using tickets.