nextcloud / nextcloud/nextcloudpi
Updating major versions with "0"
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
How it is at the moment
If updated from more than one major version behind the current version the user has to use the exact version of NC into the ncp-update-nc panel.
For example updating from NC version 23 should be done by manually loading NC v.24.0.8.
After that the user can use the "0" to get to the current version of NC25.
How it could be
If the user enters the "0" the newest version of the major version gets loaded. By using "0" again NC gets updated to the to the next major version even if this is not the most current major version.
This would make updating more simple for users.
Not sure if it is possible. Idea is from this forum question (German).
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 ncp-update-nc panel and the version-selection logic it uses. Trace how entering "0" currently loads a version, then determine how successive entries should select the newest version of each next major release; done means multi-major upgrades no longer require manually entering an exact intermediate version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100