Release Tracking

[github-actions]

This is a scheduled issue for tracking the release between Monday, December 2nd and Monday, December 16th

Last week	Value
Issue	Release Tracking
Conductor	@francinelucca
Release Pull Request	Link
Integration tests	Link

Timeline

• Monday, December 2nd
  • @TylerJDev - Review lab testing, debugging failing tests
• Tuesday, December 3rd
  • @TylerJDev - "Soft" deploy lock lifted, put release (v37.6.0) in merge queue
  • Merged!
• Wednesday, December 4th
  • Investigating timeouts in Integration Tests
• Thursday, December 5th
  • Investigating timeouts in Integration Tests, found offending PR
• Friday, December 6th
  • Diagnosed timeouts to be due to css transformation, incremented test timeouts, investigating new errors since release branch updated
• Monday, December 9th
  • got dotcom CI to green and did some preliminary testing ahead of deployment.
  • Published v37.7.0 with intention to deploy to dotcom next day
• Tuesday, December 10th
  • Release attempted, had to rollback due to bug identified during rollout testing .
  • Worked with @jonrohan on fix for bug and published v37.7.1, ran integration tests with intention to deploy to dotcom next day.
• Wednesday, December 11th
  • Updated dotcom to v37.7.1
  • Ran CI on new release PR (v37.8.0)
• Thursday, December 12th
  • Released patch version 37.7.2 for visual regression introduced in TokenBase
  • Updated dotcom to v37.7.2
  • Started testing on v37.8.0
• Friday, December 13th
• Released v37.8.0
• Was on merge queue to deploy to dotcom practically all day but ultimately had to get off because hadn't deployed by EOD, passed release testing notes onto next RC @joshblack
• Monday, December 16th

Checklist

• Checks have passed on the integration Pull Request downstream
• Release tracking Pull Request has been merged
• Stable release available on npm
• Downstream repos have been updated to latest

Notes

[TylerJDev]

Continuation from #5307 since it was closed, and my (hopefully) last update for v37.6.0.

I just put v37.6.0 in the merge queue for Dotcom, as the "soft" deploy freeze was lifted yesterday evening. I was able to clear a few of the flaky tests by increasing the timeouts in the test by around 5 seconds. While debugging the flakiness, I've noticed that some tests take slightly longer to finish compared to our most recent release in Dotcom (v37.4.0). This is what caused some of the tests to fail, as the increase in time was just enough to cause the tests to timeout (more context in my previous comment). I wasn't able to figure out the exact cause, but it appears to be a gradual increase in time taken throughout the commits made in Primer/React.

There wasn't one PR that caused the increase in time; it was the combination of all commits that seems to have increased the time taken in some tests. I think we could potentially investigate this more if we run into this issue in the near future, but for now, the increase in timeouts should be okay.

[francinelucca]

Time commitment:

• Assisting v37.6.0 deployment: 2hrs
• Investigating CI failures in v37.7.0: ~8 hours
• Releasing/Testing/Deploying/Rolling back v37.8.0: 4hrs
• Releasing Patch version v37.7.1: 1hrs
• Testing/Deploying Patch version v37.7.1: 4hrs
• Releasing Patch Version v37.7.2: 1hrs
• Testing/Deploying Patch version v37.7.2: 3hrs
• Testing v37.8.0: 2hrs
• investigating/Fixing visual regressions v37.8.0: 2hrs
• Re-Testing/Releasing v37.8.0: 1hrs
• Attempting v37.8.0 deploy: 1hrs (had to get off merge queue ultimately)

Total: ~29 hrs over two weeks CC: @lesliecdubs