Skip to content

Deploy Checklist: New Expensify 2021-08-25 #4828

Closed

Description

@OSBotify

Release Version: 1.0.90-2
Compare Changes: production...staging

This release contains changes from the following pull requests:

Deploy Blockers:

cc @Expensify/applauseleads

Activity

  1. isagoico commented on Aug 25, 2021

    @isagoico

    Starting QA 🚀

  2. roryabraham commented on Aug 26, 2021

    @roryabraham
    Contributor

    Removing the lock label to fix staging deploys

  3. isagoico commented on Aug 26, 2021

    @isagoico

    Everything was a pass here 🎉 https://github.com/Expensify/App/actions/runs/1168597268
    Only thing is that I still don't see the "Deployed to staging" messages, can we ignore that and start QA? CC @roryabraham

  4. roryabraham commented on Aug 26, 2021

    @roryabraham
    Contributor

    Yes, those will not appear because of the bug that existed when we ran the prod deploy. Ignore and begin QA please.

  5. isagoico commented on Aug 26, 2021

    @isagoico

    Starting QA 🚀

  6. isagoico commented on Aug 27, 2021

    @isagoico

    #4793 (comment) Resolved - Checking it off

  7. 24 remaining items

  8. roryabraham commented on Aug 31, 2021

    @roryabraham
    Contributor

    Trying that one more time after merging #4940

  9. added and removed on Aug 31, 2021
  10. roryabraham commented on Aug 31, 2021

    @roryabraham
    Contributor

    Okay, staging deploy for v1.0.90-0 is running here. Once that's done, feel free to begin QA (regression + testing unchecked PRs).

  11. isagoico commented on Aug 31, 2021

    @isagoico

    Starting QA!

  12. isagoico commented on Aug 31, 2021

    @isagoico

    We're almost finished with QA, all PRs have been tested and I already updated the checklist with the results.
    These 2 PRs have unresolved comments:

    1. Refactor the componentDidUpdate method for ReportActionCompose #4768 (comment)
    2. Link Workspace ID to reimbursement account setup so it is accessible during validation step #4923 (comment)

    #4880 is failing because of #4958 (It's currently being fixed 🎉)

    On regression, we haven't found any issues or deploy blocker yet. Still about 25% left in the TestRail.

    CC @roryabraham

  13. roryabraham commented on Sep 1, 2021

    @roryabraham
    Contributor

    Please retest #4880 / #4958 in version 1.0.90-2, being deployed here

  14. isagoico commented on Sep 1, 2021

    @isagoico

    Checking off #4880 since it's a pass 🎉

  15. roryabraham commented on Sep 1, 2021

    @roryabraham
    Contributor

    @TomatoToaster is going to QA #4923 internally, but since it's still hidden behind a beta, I'm not going to block the production deploy on it. So I'm going to go ahead and check it off on the checklist and run a prod deploy.

  16. isagoico commented on Sep 1, 2021

    @isagoico

    @roryabraham We're about to finish the regression testing, only 10% left, should be done in a little bit.

  17. isagoico commented on Sep 1, 2021

    @isagoico

    It's finished! feel free to trigger the Prod deploy 🎉 (no deploy blocker were found!)

  18. TomatoToaster commented on Sep 1, 2021

    @TomatoToaster
    Contributor

    Just noting that this one is QA'ed and passed too: #4923 (comment)

  19. roryabraham commented on Sep 1, 2021

    @roryabraham
    Contributor

    :shipit:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions