UMass-Rescue / UMass-Rescue/RescueBox
Rescuebox : Upgrade process for the product
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 15
- Avg merge
- 14h 42m
- Merged PRs (30d)
- 7
Description
current release of rescuebox is 2.1.0, its distributed as an exe on windows that installs backend , frontend and pre-reqs
we have a new release or patch for a plugin , how do we provide a customer upgrade feature.
one possible soln:
we provide a patch exe , that checks current product /db version , confirms no tasks are in flight , runs frontend db updates and replaces backend python server. customer restarts the app and is able to use the patched setup
we provide a new major release with new plugins , this one may or may not be backward compatible ,
this should migrate data from previous version to new version
remove old version atrifacts
customer starts new version of app, and is able to use all features , plus old plugin data is available in new environment.
all of this is automated.
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
No files, tests, or entry points are named. Start by mapping the Windows EXE’s installed frontend, Python backend, prerequisites, and database/version state; done means an agreed automated path for patches and major releases that handles in-flight tasks, compatibility and data migration, artifact removal, and restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100