Firmware bugs and features tracker
177 views
Skip to first unread message
bobc
Jul 7, 2012, 6:40:14 AM7/7/12
to r2c2-repr...@googlegroups.com
Github provides a useful and easy to use tracking system: https://github.com/bitboxelectronics/R2C2_Firmware/issues
I think we have noted several issues which are in danger of being forgotten about, it would be really useful to get these into issue tracker.
Don't be too worried about raising things that are not confirmed bugs, we can always close things later. It is best to get some discussion in the group before raising issues or making fixes to let everyone know what is going on and avoid surprises.
A suggested workflow for bugs/change requests is as follows.
1. raise issue, status = New
2. Discuss issue in group.
a) if verified bug, status = Bug
2b) if not a bug, status = Not a bug
2c) if change request, status = Feature Request
3. discuss proposed fix in group and achieve consensus
4. developer can implement fix on suitable branch, Status = Fix submitted
5. a tester should confirm the fix works, and does not introduce other problems, status = Fix verified
6. an integrator merges commit to a release branch and checks it is stable. When release is made, issue status = Released
7. Ideally the submitter should confirm the fix satisfies their problem, and the issue can be closed.
I think we have noted several issues which are in danger of being forgotten about, it would be really useful to get these into issue tracker.
Don't be too worried about raising things that are not confirmed bugs, we can always close things later. It is best to get some discussion in the group before raising issues or making fixes to let everyone know what is going on and avoid surprises.
A suggested workflow for bugs/change requests is as follows.
1. raise issue, status = New
2. Discuss issue in group.
a) if verified bug, status = Bug
2b) if not a bug, status = Not a bug
2c) if change request, status = Feature Request
3. discuss proposed fix in group and achieve consensus
4. developer can implement fix on suitable branch, Status = Fix submitted
5. a tester should confirm the fix works, and does not introduce other problems, status = Fix verified
6. an integrator merges commit to a release branch and checks it is stable. When release is made, issue status = Released
7. Ideally the submitter should confirm the fix satisfies their problem, and the issue can be closed.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages