-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy Checklist: Expensify.cash 2021-07-14 #4046
Comments
@roryabraham were good to start QA right? |
Starting QA |
#4066 is unreproducible, so I've checked it off the list |
@isagoico @mvtglobally I went through and checked a bunch of items that should not be only this checklist. I checked them off instead of deleting them so I don't have to do it again if the issue is updated and they're added back again. Sorry about the 🐛 – it disappeared on its own for a while, then came back on it's own 😠 |
Hello! It seems like we somehow got into a weird state where there was somehow a diff between staging and main at the time of the normal staging deploy for So @isagoico @mvtglobally when QA is done, let's just remove the lock label on this and add it back tomorrow when you're ready to begin QA. Thanks! |
#3988 leaving this PR unchecked so it's tested on the next QA run |
#4073 should be resolved on version 1.0.78.2 which is on staging. Feel free to test it on ios or android to confirm. |
I want to test #3383 on this checklist, so ping me when you're ready to begin QA and I can assign the lock label myself. cc @parasharrajat |
@roryabraham you can go ahead and add the lock label when needed. I can set up and begin QA tomorrow morning so we can start testing early in the day. |
Checking off #4084 (comment) as per the comment confirming it works ✅ |
Regression is finished!
PRs are finished too! These Internal QA PRs are missing QA (CC @marcaaron) :
Thanks! |
I'm looking for someone to help test #3967, but I don't think it needs to block the next release build of Expensify.cash. The feature is still behind a beta and we can keep testing until it's ready to come off the beta. Edit: We tested it and it passed |
Checking off #4075 |
@AndrewGable The checklist issue is back, I think there was a CP and a bunch of PRs (that are not in staging) were added to the list. I gave it a look and I think none of these should be in the checklist:
Thanks in advance! |
Mentioned in Slack, but what do we usually do for this type of bug? Do we just check those items off? |
Yes! They can be checked off and we just have to keep an eye if they get added to the new checklist (after the production deploy) |
Went through to double-check those and checked off the following because they haven't been deployed to staging yet:
I didn't check off the |
Also checking off #4110 (comment) - based on the comment we're not labeling it a deploy blocker |
@AndrewGable @Jag96 I retested both the CPd PRs and the missing deploy blocker issue and it was a pass 🎉 All items are checked and we should have a green light to do a prod deploy. Only thing that worries me a bit is this issue #4066 which I'm still able to reproduce on Windows 10 (only on staging) but it was discarded as Deploy blocker. |
I agree that issue does look relevant still, but I agree we can move forward with a production deploy with that known issue. |
Also.. I was thinking maybe we could get a notification to @Expensify/applauseleads every time there are Cherry Picks that need QA (from us), currently I have to manually check if there has been any CPs and I could take a while before noticing there was one. Let me know what you think guys think, I'm sure it would help us to retest the fixes faster 😬. |
Release Version:
1.0.79-3
Compare Changes: production...staging
This release contains changes from the following pull requests:
Deploy Blockers:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: