Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Pre-) release 1.20.0 #2733

Closed
timgl opened this issue Dec 10, 2020 · 3 comments
Closed

(Pre-) release 1.20.0 #2733

timgl opened this issue Dec 10, 2020 · 3 comments
Labels
sprint Sprint planning

Comments

@timgl
Copy link
Collaborator

timgl commented Dec 10, 2020

For this planning session, we only have a full week until christmas/new year etc so this might not be a full session. Context to decide what to work on:

  • We have customers waiting for things like BigQuery and Snowflake integrations, which will require plugins to work
  • We've had a few outages and in general CH performance has been lagging. We have a plan for a lot of this
  • It would be good to spend some time this week coming up with ambitious ideas for next year

Eric/Tim:

  • Finish backend filter refactor
  • Filter typing for frontend
  • Consistent backend tests
  • Finish insights history
  • Good error messages for timeouts (ie push to upgrade instance or contact support)

Marius/Michael:

  • Plugins on app
  • React native fix
  • BigQuery and Snowflake plugins
  • Stretch: Some UX improvements for plugins

James

  • Parts on the merge-tree
  • Migrate stuff off of Heroku
    • Plan for moving of Postgres
  • Get the CH tables distributed
  • Load balance CH
  • Plan for CH tables
  • Document all of it in terraform

Paolo

  • Instrumentation across the app
  • Personas stuff

Support Hero: Karl

@timgl timgl added the sprint Sprint planning label Dec 10, 2020
@macobo
Copy link
Contributor

macobo commented Dec 11, 2020

A few fun/rewarding things I'm interested in outside the current work:

If nothing else improved sessions filtering needs work as well.

@paolodamico
Copy link
Contributor

From the last release, I suggest keeping the data instrumentation piece to have more reliable numbers as we work through retention optimization. I'd also like to start working on some retention stuff to identify our key personas that we retain best.

@Twixes
Copy link
Collaborator

Twixes commented Jan 4, 2021

Closing in favor of #2842.

@Twixes Twixes closed this as completed Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sprint Sprint planning
Projects
None yet
Development

No branches or pull requests

4 participants