As of 6/3/2016 payments-wiki does not closely track production MW, and we don't have a great staging process for deployment. We have most of the tools and processes we need, but they aren't aligned well and some procedural and tool modifications are in order.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T88657 Fundraising Tech Staging (tracking) | |||
| Invalid | Jgreen | T136963 overhaul payments-wiki deployment process | |||
| Restricted Task | |||||
| Declined | Spike | None | T130658 Spike: decide how payments-wiki deployment process should relate to the core MW deployment process | ||
| Invalid | Jgreen | T97745 Adjustable load balancer to direct small samples of donors to staging payments | |||
| Resolved | Spike | Jgreen | T112857 Spike: How to configure a staging server for payments? | ||
| Resolved | Jgreen | T136966 evaluate scap3 as a possible replacement for FrDeploy tools | |||
| Restricted Task |
Event Timeline
Comment Actions
This is a vague/existential task, although nice to have it's not clear enough what we're trying to achieve to formulate next steps, so the task ends up being clutter. Closing as invalid.