Comment 42 for bug 1779205
Revision history for this message
| Lance Bragstad (lbragstad) wrote Re: GET /v3/OS-FEDERATION/projects leaks project information | #42 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
The description in comment #41 looks good. The patch is pretty trivial and it won't take much to get it proposed to the affected releases. Just for clarity though, here is the summary of proposing the patch from comment #17 to all supported branches:
master: Developed for Rocky, no conflicts.
stable/queens: Patch cleanly cherry-picked from master.
stable/pike: Patch didn't apply cleanly due to internal changes to use a different dependency registry. The fix should still be trivial to apply since it's not using the old or new dependency registry directly (but it won't be exactly like the patch applied to master).
stable/ocata: Same conflict as noted with stable/pike.
Thoughts on the cases for stable/pike and stable/ocata?
Since we have at least 4 keystone folks on this thread, I think we can schedule a time to fast-track the fix and backport it through the supported branches as soon as the VMT gives us the nod. I'd also like to get at least two keystone cores to +2/+A the patch in comment #17 prior to proposals to gerrit (in order to keep review time to a minimum after public disclosure).