Skip to content

Instantly share code, notes, and snippets.

@nalesandro
Last active November 23, 2016 21:19
Show Gist options
  • Save nalesandro/42d409fd2a2524642a765b5711e01ba1 to your computer and use it in GitHub Desktop.
Save nalesandro/42d409fd2a2524642a765b5711e01ba1 to your computer and use it in GitHub Desktop.
What all's left to do to have walrus replace bucket for new customers

Not done/decided

Must-have

nada

Really really nice to have

Improve the default welcome email

  • Who: Nick
  • When: In dev, wait for Bill to push to prod

CSV export should have data in columns

Integral consumes walrus supporters

People service consumes walrus supporters

  • Who: Stephen
  • When: TBD
  • Deets: err

Done/decided

gw.js support for supporter collection

Automatically create supporters collection

Release walrus support in analytics_api

FE support for analytics/export

Make 2016-08-04 the default API version

  • Who: Gabe
  • When: DONE

Sync legacy and new Bucket data over to Walrus

Update Supporter docs

Send emails on record create

Do we create the supporters collection/schema for customers?

  • Answer: Yes. Done and communicated to customers manually until admin/admin backend supports it

Latest Walrus, with method-level perms, deployed to prod

  • Who: John
  • When: 9/20ish

REX routes in prod

  • Who: John
  • When: 9/20ish

Set up DD monitors

  • Who: John
  • When: 9/21

Future

Migration plan for existing Bucket customers

Configure>Collections in Admin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment