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.

Sign up for GitHub

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

Jump to bottom

Release 1.17.0 - 12 November 2020 #2046

Closed
1 task done
timgl opened this issue Oct 27, 2020 · 12 comments
Closed
1 task done

Release 1.17.0 - 12 November 2020 #2046

timgl opened this issue Oct 27, 2020 · 12 comments
Labels
sprint Sprint planning

Comments

@timgl
Copy link
Collaborator

timgl commented Oct 27, 2020 •
edited by paolodamico
Loading

Priorities

  • core analytics UX improvements
  • Initial user deployment experience improvements

James G

  • Documentation & runbooking
  • Persons on events
    • Get events and people on dynamoDB
    • Table in ClickHouse with person_ids
  • Move other topics to proto
  • Feature flags client libraries

Tim

  • Think/redesign actions
  • Clickhouse query improvements/speed up
  • Sentry integration
  • Create an automatic rotation of customer support
  • Add more 'empty states' App feels broken after a fresh install #2091
  • Find and squash UX improvements
  • Clickhouse refactoring

Eric

  • Clickhouse refactoring / stable
  • Retention frontend improvements

Marius

  • Crank out example plugins
  • Security / performance of plugins
  • World-class documentation of plugins (how to create your first plugin)
  • Test-suite against a local plugin
  • Posthog-js-lite improvements for plugins
  • Create plan for moving from posthog-js to posthog-js-lite
  • Moving app to typescript
  • React Native bug
  • Adding feature flag to php/ruby library

Karl

Paolo

Michael
@timgl timgl added the epic label Oct 27, 2020
@paolodamico paolodamico added sprint Sprint planning and removed epic labels Oct 27, 2020
@paolodamico
Copy link
Contributor

paolodamico commented Oct 27, 2020 •
edited
Loading

Using release label that we used for previous one.

Things I'm keen on getting done for next release:

General

Myself

@yakkomajuri
Copy link
Contributor

Product

I want to reiterate the need for squashing bugs, although many are indeed CH-related.

#2010, #2017, and #2047 are examples of bugs related to our core functionality that we regularly demo and "brag about".

Myself

As for what I'll do on the next release cycle, me and @jamesefhawkins decided I should own a significant push for content creation and distribution, in order to trial different approaches and determine what works best.

That will take up the entire cycle for me, and I'm setting the ambitious goal of writing up 8 new pieces.

I will not only be writing, but also distributing, marketing, etc.

@paolodamico
Copy link
Contributor

paolodamico commented Oct 27, 2020 •
edited
Loading

Agree with squashing bugs, particularly related to core functionality, adding #2049, #1843, #1959, #1909.

@EDsCODE
Copy link
Member

EDsCODE commented Oct 29, 2020 •
edited
Loading

Clickhouse is near fully deployed. There are optimizations that still need to be done bu otherwise handling our own volume is very doable.

My priorities/options:

  • continue cleaning up clickhouse so that it's easy to build off of
  • go on bug squashing mode for 2 weeks

General Idea:

  • I'd be a fan of revisiting the staging environment setup. Getting a really good staging environment to sit before prod would really help our process as we're starting to have a bunch of people working on a bunch of different things that should get some exposure before launching on prod

@Twixes
Copy link
Collaborator

Twixes commented Oct 30, 2020 •
edited
Loading

I'll be off for the second half of this release, so somewhat limited, but I do have some ideas that I'd like to take care of personally in the next week:

  1. Refactor /api/user to use DRF like the rest of our web API (backend already done in PR Refactor /api/user with DRF #2111, just requires frontend adjustments), which is a long-standing hindrance.
  2. Further demo improvements (epic [EPIC] Great demo environment #2128).
  3. Smooth out the UX inconsistencies/bugs that we have, since they continue to be visible and we have a solid list of them, also some projects/orgs UX improvements (PR Org/projects UX enhancements #2145).

@macobo
Copy link
Contributor

macobo commented Oct 30, 2020

Input is focusing on what I can help with and am interested in. This list is too long for 2 weeks - hoping to whittle it down by discussion.

1. Session recording

Session recording is live and a bunch of potential features are now documented in our issue tracker. However instead of solving them, I'd love to wait a bit and see how customers are using the feature.

Known TODOs:

  1. Set up key metrics for session recording
  2. Join in on customer calls for clients who have been using the feature.

2. Cloud / Self-hosted stability

Two motivators here:

  • Getting more context and be of help with extinguishing fires. James is overloaded.
  • My own experience with setting up and managing a self-hosted instance has been painful.

Open question: How much do we want to invest into non-cloud at this point in time?

Cloud:

Self-hosted/Cloudformation:

3. Posthog.js

It's an open secret the code in posthog-js is kind of 💩, so we need some focus to fix issues like:

4. Misc features (feature flags & toolbar)

5. Clickhouse

Through happenstance I now have quite a lot of clickhouse theoretical knowledge but not a lot of practice. I'd love to put some solid focus in with optimizing/building/etc, but don't have any specific tickets in mind. :)

6. Tests

Our tests have been unstable. #2136

@jamesefhawkins
Copy link
Collaborator

jamesefhawkins commented Oct 30, 2020 •
edited
Loading

For me personally:

Last week

  • working on handing over context (!), finances, legal and HR related items so @piemets can operate autonomously. I think this is 85% done by there are a couple of bits like HMRC and hand holding needed for next week to properly complete this.
  • building pipeline for the designer and full stack developer role. I've kept the bar very high but the designer role has taken more time than I had hoped as the response rate was worse than usual.

Next 2 weeks

  • Keep recruiting for these two roles. I would aim within one more week to have solid designer AND full stack developer pipelines so we realistically have the person we're going to hire for both roles talking to us.
  • Make sure we properly promote plugins and session recording on Twitter / Users slack etc so we actually get usage from them so we can learn from users what the reaction is.
  • Support Yakko and Lottie in going deep on understanding how to grow our audience size through content. This will be probably 25% of my time this week coming (mainly on the planning side) and more like 50% the week after (QA, building campaigns and tweaking them after go live) I would expect.

@jamesefhawkins
Copy link
Collaborator

  • Release Sentry js integration

To clarify, as a user facing feature right?

@jamesefhawkins
Copy link
Collaborator

  • make more prominent (make it feel more 'live')

We should start by looking at session recording tools and working out what their functionality is since they'll have thought hard about this.

For us specifically, I can see a bunch of cool places:

  • Somehow in feature flags (ie 'I want to watch a user using this new feature')
  • In funnels 'I want to watch what went wrong when people didn't convert'
  • In user profiles 'I want to watch what this user did'
  • and integrated with the sentry integration perhaps 'I want to watch what went wrong when this error appeared'

@mariusandra
Copy link
Collaborator

mariusandra commented Oct 30, 2020 •
edited
Loading

next 2 weeks:

  • create a bunch of plugins
  • clean up and refactor plugins (interface, security, scalability, etc, see the epic)
  • posthog-js-lite
  • typescript migration
  • make the frontend better
  • show some love to the integrations (bug with android react native times, feature flags to things)

@lottiecoxon
Copy link
Contributor

Next two weeks:

  • Session Recording Feature Page (#548)
  • Finish careers page (#486)
  • Plugins product image tweaks (#505)
  • Push out PR changes for team page (#485)
  • (please let me) redesign the landing page ?
  • Slowly introduce more 8 bit style artwork into webpages so the contrast between the two art styles merges in a harmonious way. (+could also start work on animations in this style to 'liven' up the pages

@lottiecoxon
Copy link
Contributor

OH AND

  • 404 page design

@paolodamico paolodamico mentioned this issue Nov 9, 2020
Merged
@Twixes Twixes closed this as completed Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sprint Sprint planning
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@mariusandra @macobo @timgl @Twixes @paolodamico @EDsCODE @yakkomajuri @jamesefhawkins @lottiecoxon