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

Put Plugins out of beta #1065

Closed
wants to merge 1 commit into from
Closed

Put Plugins out of beta #1065

wants to merge 1 commit into from

Conversation

Twixes
Copy link
Member

@Twixes Twixes commented Mar 5, 2021

This removes statements of Plugins being in beta. Just removes for now – though in some places we may want to introduce new wording to replace the old one, e.g. that Plugins are now a core feature, required to run PostHog etc.
Pending PostHog/posthog#3557.

@jamesefhawkins
Copy link
Contributor

@Twixes happy to merge now?

@yakkomajuri
Copy link
Contributor

Don't think we're ready yet - I think we decided to keep the Beta tag on for a little longer

@jamesefhawkins
Copy link
Contributor

Nudge (are plugins still in beta? Ok if so)

@mariusandra
Copy link
Collaborator

Perhaps we could go with "Release Candidate 1"?

It's on me that the communication around this hasn't been clear, but if possible, I'd like to keep plugins as "beta" for one last release. We just added a bunch of brand new tools (console logs via clickhouse, job/retry queues via postgres, etc) that are not tested at scale and are beta by definition. What's more the beta label allows us to do somewhat breaking changes (like removing session recordings from processEvent, which we did now). This freedom gives us a lot of flexibility in figuring out what we really want.

In any case, the main issue is that the job/retry queues, which are essential for bulletproof data exports, are legitimately beta. Everything else works, but with a strong focus on data exports, I'd really like to get them solid before officially blessing the system with a "release".

That said, the system is working pretty well overall, and I could be convinced to remove the beta label if there's a strong marketing push planned e.g. mid-release. Alternatively, as I said at the top, we could replace "BETA" with "RC1".

@jamesefhawkins
Copy link
Contributor

jamesefhawkins commented May 13, 2021

if there's a strong marketing push planned

Not currently - I suspect we should open up the range of data that plugins have access to before doing a big HN type thing (in addition to being confident that they work reliably in their current form at scale). Specifically, user profiles will enable integrations with ie CRMs that I think would make them significantly more powerful for startups. I'd also add the disclaimer that it matters more our data warehouse integrations are awesome than we extend plugin functionality for the next couple of weeks too - so don't drop everything to do this!

@Twixes Twixes closed this Jun 29, 2021
@Twixes Twixes deleted the out-of-beta-plugins branch June 29, 2021 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants