-
Notifications
You must be signed in to change notification settings - Fork 3k
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-04-13 #2380
Comments
Regression is finished!
PRs are finished too.
Thanks! |
Unlocking and relocking to see if GitHub's wonkiness with the branch rename will self-resolve. |
Okay, staging seems to be back to normal. Going to unlock this, because Applause is getting a day off of QA due to the technical issues we had today. We'll resume QA tomorrow with a clean slate 😄 |
Regression is finished!
PRs are finished too.
PR #2022 is still unchecked because, as mentioned here, #2022 (comment) we don't have access to the split bill feature to test this. Thanks! |
Looks like something weird happened here and the lock label was left on this issue over the weekend. Removing now, @isagoico feel free to re-add when you are ready to begin QA |
Mmm weird I just added it a few minutes ago so we can start QA |
Oh, sorry about that. This is what I'm seeing: My mistake @isagoico, but maybe in the future it's best to comment saying "starting QA now" or something so the chain of events is a little clearer. |
I saw "you added and removed the label", but then the label was still on the issue... confusing 😕 |
Must be because I don't use darkmode |
Sorry for the troubles today, unlocking again, and can relock after #2461 is merged. |
Regression is finished! PRs are finished too
Thanks! Status of unchecked PRs below:
|
Regression is finished! PRs are finished too.
Thanks! |
Checking off |
Can confirm this can't be tested externally. I've marked it off the list. |
As discussed in the issue, we're going to remove the |
btw @isagoico this annoying GH bug is back... this is what I'm seeing on the issue right now: But I know you added the lock label just a few hours ago. I'm not sure what the process is for reporting bugs on GitHub, but in the interim can you please just leave a comment when you add the lock label so that the audit trail is clearer? Normally you wouldn't have to, but it is just a workaround for the time being. |
Regression is done. Removing the lock label! |
Chat Regression is finished! |
Starting QA setup! Adding the lock label |
Sorry @isagoico, I am expecting the iOS deploy to fail. We have a potential fix that was merged just moments after you added the lock label here (I am actually unsure whether or not that PR is included in the current deploy, but I think not). If the iOS deploy does indeed fail, we'll need to remove and reapply the lock label this morning. |
Looks like the iOS deploy was a success, so you're good to begin QA @isagoico |
#2506 (comment) - Will be fixed separately, checking it off |
Regression is finished!
PRs are finished too!
Thanks! |
Starting QA! Adding the lock label |
Regression is finished! PRs are finished too! |
As commented in the issue, I removed the deploy blocker label from #2620 and checked it off on the checklist. |
Checked off #2497 |
Starting QA! |
Regression is finished! PRs are done too |
So since #2636 is not a deploy blocker, we can run a prod deploy! |
Release Version:
1.0.34-0
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: