Manually override staged roll out
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: check for update
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
We do a stage rollout, but if admins want to have nevertheless a direct upgrade, it should be possible.
- inform about staged rollout, so that admins know why they do not see latest version
- have an "override button", which is manual, so that concept of stage rollout is still working
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 tracing how the updater handles staged rollouts and how it presents available versions to administrators. Define the admin-facing notice and manual override flow, then verify that overriding permits a direct upgrade without disabling staged rollouts for other users.
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
- 45/100