Skip to content

Deploy Checklist: New Expensify 2022-03-24 #8305

Closed

Description

@OSBotify

Release Version: 1.1.46-3
Compare Changes: production...staging

This release contains changes from the following pull requests:

Internal QA:

Deploy Blockers:

cc @Expensify/applauseleads

Activity

  1. OSBotify commented on Mar 24, 2022

    @OSBotify
    ContributorAuthor

    🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.1.46-0 🚀

  2. roryabraham commented on Mar 24, 2022

    @roryabraham
    Contributor

    YOOO I am unable to reproduce #8308 – can you retest please? It worked as expected me on 1.1.46-0

  3. mvtglobally commented on Mar 25, 2022

    @mvtglobally

    Desktop build is still 1.1.44-4. We tried to download from URL as well and it is not updating. Pls let us know if anything can be pushed there - RESOLVED

  4. OSBotify commented on Mar 25, 2022

    @OSBotify
    ContributorAuthor

    👏 Heads up @Expensify/applauseleads 👏
    A new pull request has been 🍒 cherry-picked 🍒 to staging, and will be deployed to staging in version 1.1.46-1 🚀

  5. OSBotify commented on Mar 25, 2022

    @OSBotify
    ContributorAuthor

    🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.46-1 has been deployed to staging 🎉

  6. OSBotify commented on Mar 25, 2022

    @OSBotify
    ContributorAuthor

    👏 Heads up @Expensify/applauseleads 👏
    A new pull request has been 🍒 cherry-picked 🍒 to staging, and will be deployed to staging in version 1.1.46-2 🚀

  7. OSBotify commented on Mar 26, 2022

    @OSBotify
    ContributorAuthor

    🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.46-2 has been deployed to staging 🎉

  8. mvtglobally commented on Mar 28, 2022

    @mvtglobally

    #8160 (comment)
    #8205 (comment)
    #8226 (comment)
    #8265 (comment) - can we check it off?

    Deploy blocker #8019 failing due to #8308 we are retesting

    #8173 is failing this, App is freezing, should we treat it as deploy blocker? #8173 (comment)
    #8174 is failing #8313, checking off as repro in PROD
    #8195 is failing due to #8311. Its a new feature, do we want to treat is as Blocker?
    #8257 is failing due to #8295. Not blocker checking off

    #8063 - InternalQA
    #8204 is a PR from previous deploy. Can I just check it off as it wasn't deployed again and not in PROD yet

  9. roryabraham commented on Mar 28, 2022

    @roryabraham
    Contributor

    #8160 was verified by a number of people on both x64 and arm. Checking it off.

  10. roryabraham commented on Mar 28, 2022

    @roryabraham
    Contributor

    Deploy blocker #8019 failing due to #8308 we are retesting

    @mvtglobally Does that mean that #8308 is still reproducible?

  11. mvtglobally commented on Mar 28, 2022

    @mvtglobally

    @roryabraham Checking off #8308. Its not repro

  12. mvtglobally commented on Mar 29, 2022

    @mvtglobally

    @roryabraham @timszot Just few things pending on this checklist. Can we close it off today

    Deploy blocker #8019 fix is pass, checking off
    #8063 - InternalQA - Can someone validate and checkoff?
    #8205 (comment) - InternalQA - Can someone validate and checkoff?
    #8173 is failing this, App is freezing, should we treat it as deploy blocker?
    #8195 is failing due to #8311. Its a new feature, do we want to treat is as Blocker?
    #8204 is a PR from previous deploy. Can I just check it off as it wasn't deployed again and not in PROD yet
    #8226 - we are retesting and will check off
    #8265 (comment) - can we check it off?

  13. timszot commented on Mar 29, 2022

    @timszot
    Contributor

    OK, I'm going through all of these.

    #8063 - InternalQA - Can someone validate and checkoff?

    Checked off, there's a comment saying it worked.

    #8205 (comment) - InternalQA - Can someone validate and checkoff?

    Pinged in the PR and in internal Slack channels.

    #8173 is failing this, App is freezing, should we treat it as deploy blocker?

    Asked in PR to confirm my thoughts, but no, I don't think we need to block on this.

    #8195 is failing due to #8311. Its a new feature, do we want to treat is as Blocker?

    I would say no it's not worth blocker for since there is a new issue opened to track the bug and it doesn't break any functionality, it's just a copy change.

    #8204 is a PR from previous deploy. Can I just check it off as it wasn't deployed again and not in PROD yet

    Checked off.

    #8265 (comment) - can we check it off?

    Looks like we can, doing it!

  14. OSBotify commented on Mar 29, 2022

    @OSBotify
    ContributorAuthor

    👏 Heads up @Expensify/applauseleads 👏
    A new pull request has been 🍒 cherry-picked 🍒 to staging, and will be deployed to staging in version 1.1.46-3 🚀

  15. OSBotify commented on Mar 29, 2022

    @OSBotify
    ContributorAuthor

    🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.46-3 has been deployed to staging 🎉

  16. mvtglobally commented on Mar 29, 2022

    @mvtglobally

    Checking off 8226, #8195

    @timszot We are down to #8173 and #8205 (comment)

  17. timszot commented on Mar 29, 2022

    @timszot
    Contributor

    Checking off #8173

    Only InternalQA for #8205 left

  18. mvtglobally commented on Mar 30, 2022

    @mvtglobally

    @timszot any update on the last PR? hoping for a new Deploy today

  19. neil-marcellini commented on Mar 30, 2022

    @neil-marcellini
    Contributor

    I'm doing the QA now, the engineers tagged are outside the US, and the currency was IP based, so they couldn't QA it.

  20. neil-marcellini commented on Mar 30, 2022

    @neil-marcellini
    Contributor

    QA passed for #8205! Wow, quite a struggle to test that one. I had to use my own bank account and debit card for testing.

  21. timszot commented on Mar 30, 2022

    @timszot
    Contributor

    :shipit:

  22. SumitDiyora commented on Apr 15, 2022

    @SumitDiyora

    Checked all PRs on Production / Staging and created accessibility issues for all PRs where accessibility issues were found.
    The non-applicable PRs are - #6764, #7831, #8050, #8053, #8063, #8087, #8160, #8174, #8181, #8203, #8204, #8205, #8211, #8231, #8242, #8254, #8257, #8258, #8262, #8265, #8266, #8271
    Logged Issues - #8398, #8395, #8393, #8392, #8430, #8616, #8432, #8577, #8575, #8417, #8392, #8654, #8554, #8413, #8432, #8433, #8434, #8558, #8559, #8392, #8393, #8395, #8398, #8408, #8403, #8392, #8465, #8398, #8633, #8465, #8402, #8651, #8432, #8430, #8463, #8403, #8402, #8401
    Note: After client confirmation PR #8093 has no QA steps, and can be skipped

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