devs_discuss_test_plan.md

The table below contains what ZP and I discussed regarding the launch plan. We tried to fit that into the existing timeline with tasks we'll need to complete below that. The numbered steps represent deployments/environment changes/config changes for any of the services. The bullets are general action items and tasks. The horizontal lines separate tasks that can happen after the numbered step above them from tasks that must happen before the numbered step below them.

Step	Date	CMS	API	eGalaxy	Chase	Convio
1	June 19	ecomm	ecomm	staging	sandbox	staging
2	June 29	ecomm	ecomm	production	sandbox	staging
3	July 6	production (0%)	production	production	production	production
4	July 10	production (10%)	production	production	production	production

0. Outstanding questions that might affect timeline

• The API send donations placed with ticket orders to Convio, and does the same with memberships. Does this needs to be changed before memberships launch. If so, what change is needed? This will take some time, depending on the change.
• Which environment is WCS using to QA? We'd prefer staging so we can keep ecomm for development.
• How much other dev work will be going on during this time? Since WCS is using one environment for QA, we won't be able to use that for development. We might need to create and set up additional environments for both the CMS and the API.

---

• Viget: Rebase ecomm branches with master (CMS and API)

1. Feature Complete (June 19)

• Wcs/Viget: Thorough QA on staging
• Viget: Implement fixes based on QA

---

• WCS/Viget: Confirm plan for filtering test orders on eGalaxy production
• Viget: Rebase ecomm branches with master (CMS and API)

2. Point eGalaxy at Production (June 26)

• WCS/Viget: Thorough QA of tickets
• WCS/Viget: Thorough QA of memberships
• Viget: Fix bugs resulting from differences in eGalaxy staging and production (this is our biggest unknown).

---

• Viget: Set up splitter and admin-only access for memberships checkout (CMS)
• Viget: Add seed data for production (CMS)
• Viget: Set up configs on both ecomm production servers (API)
• Viget: Make production migrations roll-backable (API)
• WCS/Viget: Confirm plan for filtering/canceling test orders on eGalaxy production
• WCS/Viget: Confirm plan for voiding/refunding test transactions on chase production
• WCS/Viget: Confirm plan for filtering/canceling test donations on Convio (Springboard?) production
• Viget: Merge to master (CMS and API)

3. Push everything to production with memberships split at 0% (July 6)

• Viget: Monitor tickets
• Viget: Thorough QA of memberships July 7-8

---

• WCS: QA of memberships
• WCS: Confirm ready for soft launch

4. Soft launch by increasing memberships split to 10% (July 10 or whenever WCS is ready)

• Viget: Soft launch when ready(10%)

@zporter @albaer Answers to your # 0 are below. Let me know how this impacts the plan / maybe you can update the gist accordingly?

0. Outstanding questions that might affect timeline

The API send donations placed with ticket orders to Convio, and does the same with memberships. Does this needs to be changed before memberships launch. If so, what change is needed? This will take some time, depending on the change.

See https://github.com/wildlife-conservation-society/wcs/issues/2283 - No Convio integrations are needed. We should no longer be submitting to Convio at all, for donations on memberships or tickets. I thought we did this as a part of donation implementation for membership, but it sounds like we need to put in a ticket to remove the Convio integration?

Which environment is WCS using to QA? We'd prefer staging so we can keep ecomm for development.

WCS is QA-ing this week. thus, they are using e-comm (because to my knowledge, memberships are not on staging / they're not merged to master. We can tell them to shift to QA-ing on staging once we're actually at the point where we can deploy to staging, but we didn't want to delay them putting eyes on checkout till then (too risky).

How much other dev work will be going on during this time? Since WCS is one environment for QA, we won't be able to use that for development. We might need to create and set up additional environments for both the CMS and the API.

I don't understand the question. Do you mean how much other dev work outside of the membership new orders project? If so, that's TBD. I need to catch up with David about the sequencing of other work. There will at least be a small amount of dev next week, but larger efforts (moving forward with renewals or treetop adventure e-comm) is TBD based on my discussion w/ him.

Also, few more notes:

1. Thanks for putting this together! You guys are awesome.

2. I don't understand this, though I've read it a few times:

The horizontal lines separate tasks that can happen after the numbered step above them from tasks that must happen before the numbered step below them.

For the rest of the details, I slightly extended our standup tomorrow morning to discuss and fine-tune the plan. After that, I'll convert the details into a client-facing launch plan similar to what we did with tickets that we can share and discuss in our Thursday check-in with WCS.