Bug fixing Mentality

@nicknacky

Take a look at all the critical bugs that are tagged critical. For each one, it needs to go through this process. Order can be somewhat flexible, but I'm sure you guys are smart enough to figure it out.

Proposed Sets of Labels

Set 1: Priority

1. Critical (today)
2. Sub-critical (tomorrow)
3. Icebox (later this week)
4. Freezer (wayyyy later, like a week from now)

Set 2: Difficulty

1. < 15m
2. < 1 hour
3. 1-2 hours
4. Too long, please split

Set 3: Status

1. Please Verify
2. Closed --> ** No label needed for this
3. Help Plz

Set 4: Platform (1-2)

1. Android
2. Windows
3. iTunes
4. Mobile
5. Browser

Set 5: Type

1. Feature
2. Enhancement
3. Bug
4. Funsies

Life cycle of a bug

• For bugs that are less than 5 minutes && an immediate solution persists, those are known as quick-fixes and you can just knock those out.
• For bugs longer than 5 minutes, create a new branch and call it "issue-{{issue number}}", If unit tests are being written, call it issue-{{issue-number}}
• Fix it efficiently -- if refactoring will take more than 15m, create separate issue && tag it with both refactoring && subcritical [Nick]
• Test it rigorously --> make sure it won't happen in any other platforms.If another bug comes in the way && is not necessary to fix the current one, create a separate issue & get back to it later.
• If you are done with the fix before the tests are ready, tag Jason && label it with "Verify Plz && assign to Jason

Life cycle of testing a bug

• Write a list of all the things you are going to test. - Workflow - Open device --> login --> become a guru - - Test on multiple devices
• Create a new branch and call it "issue-{{issue number}}", - [ ] Fix it efficiently -- if refactoring will take more than 15m, create separate issue && tag it with both refactoring && subcritical [Nick]
• Test it rigorously --> make sure it won't happen in any other platforms.If another bug comes in the way && is not necessary to fix the current one, create a separate issue & get back to it later.

Other notes

• Mentality should be getting it done so we can make the release.
• Remember that there is a time where you can do things for however long, just quickly knock out the critical ones
• Repeat until all critical are done. Then you either have tasks, factoring, or other things added for tomorrow.