希望可以考虑rollback的机制
Open
- Dominant language
- C++
- Stars
- 7k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
场景:
1. old-methodB确实有问题， 但不至于crash,
2. 打了patch后，new-methodB可能会引发更大的BUG， 比如导致crash,
3. 此时需要rollback到old-methodB
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names only old-methodB and new-methodB and provides no files or tests. Start by tracing AndFix’s Android hot-fix flow to determine where a patch is applied and what rollback trigger and state it would need; done should be defined as safely returning to old-methodB after new-methodB causes a serious failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100