FBP Go: v1.0.7
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**As a** *(User Type/Persona)* **I want** *(Feature/enhancement)* **So That** *(Value, why is this wanted, what is the user trying to accomplish)*
**Additional Context**
Release plan:
v1.0.4 internal testing
v1.0.5 internal testing
v1.0.6 RC1
v1.0.7 RC2
**Acceptance Criteria**
- [x] FBP: The percent dead fir slider showing in M1/2, it should only be showing in M3/4. PDF must only only show for M3/4; PC only for M1/2.
- [x] FBP: When switching between fuel types it remembers all settings, but resets BUI to a baseline value.
- [x] FBP: Limit slope to 60%.
- [x] FBP: Limit altitude : -200 to 3000 (might consider switching input to slider)
- [x] FBP: Altitude should specify that it's meters.
- [ ] FBP: Adding assumptions.
- [ ] Incorporate card sort feedback in advanced and or basic tab.
- [ ] Release for open testing on Apple iStore and Google Play Store (anyone with link can access it)
- [x] Re-factor - removing "basic" screen code from app (just commented out for now, in case we want to bring it back in).
- [x] FBP: Switch grass fuel load to slider? Or fix input (can't dismiss keyboard in iOS).
- [ ] FBP: Consider input option without sliders.
- [x] FBP: FFMC lower limit kept at 80 (values lower than 80 not deemed relevant).
- [ ] FBP: Incorporate card sort feedback.
- [x] FBP: Hide CFB and CFL when using grass fuel type.
- [ ] Tech: Automated build (apk + appbundle) in github workflow.
- [ ] Web: About isn't working on the web version.
**Definition of Done**
- Ready to Demo in Sprint Review
- Does what I have made have appropriate test coverage?
- Documentation and/or scientific documentation exists and can be found
- Peer Reviewed by 2 people on the team
- Manual testing of all PRs in Dev and Prod
- Merged
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the unchecked release-plan items and separating the mobile, web, build, and design work; done requires the listed acceptance criteria, appropriate test coverage, documentation, peer review, manual testing, and a merged release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions, ios
- Domain
- ci-cd, mobile, release, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100