Change logic of changelog/update notifier
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
When users upgrade to 17.0.0, they will see what's new in Nextcloud 17 thanks to the changelog server.
Unfortunately, if they upgrade from 16.0.3 to 17.0.2, they will not see what is new in 17. They might see what is new in 17.0.2 compared to 17.0.1, but that's far less interesting and relevant.
We could try to be super smart about this, but, as minor releases tend to not be so interesting for normal users, the best solution is probably to simply show the changelog of a major release once per user. So forget about minor releases, what matters is: if you move to a new major release (irrespective of the minor release you go to), show the changelog of that major release.
This has the side benefit of being more realistic with regards to how we keep the changelog server up-to-date (mostly on major releases)...
@blizzz Ack?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the changelog/update notifier and tracing how it compares the installed and target versions, using the linked changelog server for context. Done means a user moving to a new major release sees that major release's changelog once, regardless of the minor versions involved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100