element-hq / element-hq/element-web

Tighten the What's New > Changelog > Update flow and roll it out to more than Develop

Open
#26,092 4 comments 1 reaction 0 assignees View on GitHub
A-Notifications S-Minor T-Enhancement
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

![image](https://github.com/vector-im/element-web/assets/89144281/f72332ea-9f27-43ce-80a0-1dc9814b9135)

We have this in Develop only. I'd like us to polish it and consider rolling it out for other versions (Nightly, Web, & Desktop)

We need to discuss this more (and especially where it lands on our priorities list but...) I'd like to:

```[tasklist]
### Tasks
- [ ] Make the button on the left a secondary button and have it open the changelog
- [ ] Make the button on the right the primary button and have it take users straight to upgrade
- [ ] Update the layout of the changelog dialog so that it's easier to read
- [ ] Implement a changelog process internally where these are written as release notes, not links to GH tickets
- [ ] Discuss rolling it out on other versions of our product suite
- [ ] Discuss how ESS users might be able to change or tailor the content
```

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing What's New > Changelog > Update flow in Develop and the attached screenshot. Define the desired button hierarchy, changelog dialog layout, rollout targets, release-note process, and ESS customization approach; done requires agreement on these broader product decisions before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.