aj-codecov
commented
8 months ago Upgrade levers - where can we reasonably put these? What makes sense at the free and Team level?
Notification for free users should be well in advance - preferred approach would be to change the users-basic plan and not add a new plan. If blocker we can revisit. Email/in app messaging. Can we target ONLY users using flags/components in a private repo.
VSCode extension - no change needed to what's shown, labeling to show plans it applies to in the results and descriptions. Slack app - needs to remove change and focus on PR/Commit focus - what's the usage? Public API - needs to remove change and focus on PR/Commit focus - maybe not possible?
Framework: sensitive to removal, less sensitive to accidental discovery of non-core features
katia-sentry
On November 16th, 2023 we launched the Team plan, a lower cost offering designed to get people in the Codecov door. We've seen people purchase roughly 1.2 team plans per day over the first 25 days (not adjusted for weekends). We're now eyeing a more "first class citizen" rollout of the Team plan. This means it will be present on our pricing page and supported forevermore. Additionally, our current free offering will need to be scoped to be a patch only offering.
What does this entail?
Risks to extensions Making changes to the API will have a risk of breaking each of the extensions:
We will need further investigation (and code changes) on these extensions before deploying the API changes. (ie Issues 1157-1160)
However Issues 1148 - 1151 can be completed before the investigations since they are foundational work that don't actually modify the responses of the endpoints
The work below is likely doable at the same time as some of the above work as it's 75/25 platform/applications