Smack user in a face with release notes after update #7612

Open
opened 2026-01-31 01:08:41 +00:00 by claunia · 2 comments
Owner

Originally created by @zawor on GitHub (Apr 23, 2020).

Originally assigned to: @carlos-zamora on GitHub.

Description of the new feature/enhancement

Smack user in a face with release notes dialog/view/whatever you feel like appropriate after each update. It should be rather opt in feature as I can imagine not everybody wishes to see those.

It should solve (to some extent) situations like #5458 where breaking changes had limited visibility until user got hit with fallout. And those which run on Windows Store version (like I do) and don't hold their hand on the pulse of latest upcoming changes (just like me) were pretty surprised by it.

Proposed technical implementation details (optional)

In perfect world I would love to see it 1-to-1 like VS Code does. Love how they did release notes and call me pervert but I read them from cover to cover every single time. You simply get smacked with new tab with clear and well organized release notes in every time you get updated. I imagine that built in dedicated view like in VS Code may be not quite feasible in reasonable time/budget but opening browser window pointing to release notes will do the job too.

Originally created by @zawor on GitHub (Apr 23, 2020). Originally assigned to: @carlos-zamora on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Smack user in a face with release notes dialog/view/whatever you feel like appropriate after each update. It should be rather opt in feature as I can imagine not everybody wishes to see those. It should solve (to some extent) situations like #5458 where breaking changes had limited visibility until user got hit with fallout. And those which run on Windows Store version (like I do) and don't hold their hand on the pulse of latest upcoming changes (just like me) were pretty surprised by it. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) In perfect world I would love to see it 1-to-1 like VS Code does. Love how they did release notes and call me pervert but I read them from cover to cover every single time. You simply get smacked with new tab with clear and well organized release notes in every time you get updated. I imagine that built in dedicated view like in VS Code may be not quite feasible in reasonable time/budget but opening browser window pointing to release notes will do the job too. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureProduct-TerminalArea-UserInterface labels 2026-01-31 01:08:41 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 25, 2020):

Yeah, we definitely need a better on-upgrade story. I think it'd be really cool if we popped it up in an actual terminal tab. Like, using the terminal renderer and stuff.

@DHowett-MSFT commented on GitHub (Apr 25, 2020): Yeah, we definitely need a better on-upgrade story. I think it'd be really cool if we popped it up in an _actual terminal tab_. Like, using the terminal renderer and stuff.
Author
Owner

@zadjii-msft commented on GitHub (Oct 7, 2021):

@Rosefield:

It would be cool if when the terminal upgrades it showed you the changes in the new version(s). This would help with feature discovery since many users would not know/think to look at the blog posts or github release notes.

With #11308 there will be some precedence for showing non-terminal content in the terminal, and that infrastructure could potentially be used to show a modal/textbox with the release notes.

With the ApplicationState it can also store the last used version, so that a diff between old ~ new could be showed.

@zadjii-msft commented on GitHub (Oct 7, 2021): _@Rosefield:_ > It would be cool if when the terminal upgrades it showed you the changes in the new version(s). This would help with feature discovery since many users would not know/think to look at the blog posts or github release notes. > > With #11308 there will be some precedence for showing non-terminal content in the terminal, and that infrastructure could potentially be used to show a modal/textbox with the release notes. > > With the ApplicationState it can also store the last used version, so that a diff between old ~ new could be showed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7612