Changes

==Developers attention==

==Developers attention==

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 ''pushed out'' an email of 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==

==Track development and considerations==