Closed as not planned
Closed as not planned
Description
Context
There are some cases where users might not want the changelog (for Open Source, and Self-Hosted, etc).
Use Cases
- For optimised "onboarding" flows in Open-Source or Self-Hosted
- When hopping hosts, Self-Hosted installs or onto SaaS (you will see a changelog multiple times)
- When creating a custom onboarding flow into Gitpod in Self-Hosted - Self-Hosted customers often have a more "high-touch" onboarding into Gitpod than users on SaaS or in Open Source projects. The need for a self-serve onboarding is less relevant as these customers might choose to have literal in-person sessions with their users to onboard them.
Potential solutions
- Improved heuristic for when release notes are shown, e.g.
- Don't show release notes for a new project the user is opening (to the user) - prioritise the onboarding experience of the project instead of Gitpod onboarding.
- Only to users who are new to Gitpod - prioritise Gitpod onboarding over the project onboarding.
- Options for a user to disable entirely Release Notes for themselves
- Options for disabling the Release Notes + Walkthrough on a per-project basis
- Disable release notes or walkthrough on an installation level (e.g. a full Self-Hosted installation) where the company will take ownership of onboarding both into the project AND into Gitpod as a product