MobileNativeFoundation / MobileNativeFoundation/Store
Backport #658 to v5.0.x
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.4k
- Forks
- 217
- Avg merge
- 18m
- Merged PRs (30d)
- 4
Description
Summary
#658 fixes a deadlock that's been present in v5.x for a while but it's fix is only landed in v5.1.x which is still in alpha & has several breaking changes. Can we cut a v5.0.1 with this fix applied as a backport?
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 issue #658 and checking the v5.0.x branch and release process. Verify how the deadlock fix can be backported without the v5.1.x breaking changes. Done means a v5.0.1 release containing that fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100