Hi all,

Since we are worry about the internal testing that might get some real donations, here is an application named LaunchDarkly,
which can do canary release:
https://docs.launchdarkly.com/guides/infrastructure/deployment-strategies/?q=canary#canary-releases
and progressive rollout
https://docs.launchdarkly.com/home/releases/progressive-rollouts/?q=progressive
also there is a way to test the conversion rate based on form input and button click:
https://docs.launchdarkly.com/home/experimentation/stats-details/?q=conversion+rate#conversion-rate
or use the percentage rollout to do A/B testing
https://docs.launchdarkly.com/home/releases/percentage-rolloutse

let's see if it's worth to have this integrated for us to help with internal stakeholder test and if possible this could used in wikicore, that help to hide the payment method in DonateWiki, so we can control the payment method from LaunchDarkly dashboard instead of messing around Web team's code here https://donate.wikimedia.org/wiki/Template:Paymentmethod

This is a cost services, so let's do a spike first to see if we can gain some benefit from it