859
edits
Changes
Jump to navigation
Jump to search
mLine 16:
Line 16: − + −
Why you should use Bugzilla (view source)
Revision as of 17:04, 5 January 2015
, 17:04, 5 January 2015→Track development and considerations
First and foremost is that the developers do not always read the forums, so a problem that may be a bug would not get seen/flagged by them immediately. (Yes, they do pop in to the forums as and when they can, but the first things they look at are bugs.) However, Bugzilla ''pushes'' an email with any Bugzilla changes to the developers ''pro actively''. Developers can also set a variety of statuses on bugs to indicate their progress. They get notified if there is a change of status. You can also do things like set one as blocking say a release of an ISO - i.e you can't build and release an ISO until bug x, y, or z is fixed.
First and foremost is that the developers do not always read the forums, so a problem that may be a bug would not get seen/flagged by them immediately. (Yes, they do pop in to the forums as and when they can, but the first things they look at are bugs.) However, Bugzilla ''pushes'' an email with any Bugzilla changes to the developers ''pro actively''. Developers can also set a variety of statuses on bugs to indicate their progress. They get notified if there is a change of status. You can also do things like set one as blocking say a release of an ISO - i.e you can't build and release an ISO until bug x, y, or z is fixed.
==Track development and considerations==
==Tracking development and other considerations==
Next Bugzilla also provides a record of problems, fixes and any considerations, that can easily be referred too later. If developers make a fix and introduce a regression we can see exactly what went on, the thought processes, the code, verifications etc. It gives a level of quality assurance to the process. It also means that a new developer can easily read through and understand what has gone on.
Next Bugzilla also provides a record of problems, fixes and any considerations, that can easily be referred too later. If developers make a fix and introduce a regression we can see exactly what went on, the thought processes, the code, verifications etc. It gives a level of quality assurance to the process. It also means that a new developer can easily read through and understand what has gone on.
==Assist development==
==Assist development==