-
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 2024-08-19] [P2P Distance] Enable split distance requests #36967
Comments
Job added to Upwork: https://www.upwork.com/jobs/~017fd731ba8df719c5 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @jjcoffee ( |
@jjcoffee Eep! 4 days overdue now. Issues have feelings too... |
@jjcoffee Still overdue 6 days?! Let's take care of this! |
Chill, Melv ✌️ |
@jjcoffee Huh... This is 4 days overdue. Who can take care of this? |
I'm starting on this now. I will split up the plan into multiple PRs to keep each one small and focused. I will start with moving split participant normalization to Auth. Actually, now that I look more closely, it makes sense to move the creation of an individual payer account to Auth first. Then we can re-use that Auth function to create all split accounts as needed. Therefore I'll HOLD this issue on the issue to implement that part [P2P Distance] Move creating the payer account for money requests from Web-E to Auth |
On hold for a bit, moving to weekly |
On hold |
I got all the PRs up for review. 🎉 It was a lot of work and there will be some more to do 😅 |
This issue has not been updated in over 15 days. @neil-marcellini eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.18-10 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 2024-08-19. 🎊 |
Head's up, I'll be working 50% for the rest of this week and next 🌲 |
Triggered auto assignment to @twisterdotcom ( |
@twisterdotcom would you please handle payment for the C+ @mananjadhav |
@neil-marcellini what are we pricing this at? Normal $250? |
Going to go with $250 as normal here. Payment Summary:
|
$250 approved for @mananjadhav |
Enable split distance requests following this plan
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: