Offer to continue with next release
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
description
If you upgrade from, say, 17 to 20, you go through 18 and 19. If there's a newer version available, it'd be nice if the updater could already offer to continue, even better, if it were possible to add a -y and have it upgrade all the way to the end.
Would need https://github.com/nextcloud/updater/issues/320 to avoid problems!
Alternative to https://github.com/nextcloud/server/issues/2270 - instead of skipping, just run through them all. It shouldn't cause any issues, other than taking a little longer, and is faster and less risky to implement.
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 reading the constraints in issue #320 and compare the proposed approach with nextcloud/server issue #2270. Trace how the updater handles sequential releases, then verify that an upgrade can continue through every available version and that a -y option reaches the latest release without prompting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100