-
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
[HOLD for payment 2023-07-06] [HOLD for payment 2023-07-05] Removing CP Staging label #20764
Comments
Triggered auto assignment to @johncschuster ( |
I can implement this |
Am I needed on this one? |
This will be internal so you're probably good here @johncschuster |
Let's plz try to get #20791 over the finish line before we start implementation on this. |
Held on #20791 |
I think we can take this off HOLD now |
Removed label, I will remove the code now |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.33-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-07-05. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Closing - no payments here to send out here! There is one linked issue I opened up here: #21763 about the CP process but the CP Staging label is no more! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.34-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-07-06. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Problem
Coming from this thread and in the spirit of discussing the necessity of each CP, we decided to remove the CP Staging label so that NewDot CPs can only be manually CPed by App deployers after a discussion about the real need for that CP.
Why is this important
Ensures that we always discuss each CP by making authors request the CP in Slack.
Solution
Remove
CP Staging
label and its functionalitycc @Expensify/mobile-deployers
The text was updated successfully, but these errors were encountered: