====== Bugtracker (http://bugs.unrealircd.org) conventions ======

===== Reporting bugs ====

==== General bugs ====

Select 4.0-devel for 4.0 bugs, and the correct version for 3.2.* bugs. 

==== Feature suggestions ====

Set severity field to 'feature'

==== Patch submissions =====

=== CVS ===

From the CVS checkout root,

cvs diff -u > patchname.patch

=== SVN ====

From the SVN checkout root,

svn diff > patchname.patch

=== Submitting ====

Report an issue on http://bugs.unrealircd.org/ , mark severity as 'feature', attach patch and explain the patch, remember to set what version you have done it towards. Please follow coding conventions for the version.

===== General workflow =====

==== Shared QA/Committers work ====
  * Upon reporting of bug, "new" - updaters update status to 'acknowledged' (which means, we've seen the bug)

  * QA/Committers tests bug and marks it as 'confirmed' - or asks for additional information, mark as 'feedback'. If bug cannot be reproduced or is not feasible or is duplicate, close bug with proper argumentation and remove non-duplicate relations.

  * If the bug is a feature request but Severity: is marked wrong, this should be corrected to 'feature' so difference between actual bugs and feature bugs can be made. After this feature bugs follow same procedure as rest -'confirmed' will mean there's merit to the feature and work may possibly begin on it (doesn't mean feature will be included). If Severity: is 'feature' but it is not a feature request, change flag to something more fitting.
 
==== QA work ====
  * Upon bug confirmation: QA reports if this bug exists in both InspIRCd and Unreal4, and sets 'U4: Upstream notification of bug' field to 'Shared InspIRCd & Unreal4 issue reported by QA' and notifies InspIRCd Developers - if the opposite is true, set to 'U4-only issue'

  * Upon bug resolving: If QA field is "Fixed by developer, needs QA testing", QA verifies the fix, updates bug QA field to 'QA has accepted the fix'. If bug fix is not proper, QA updates bug QA field to 'QA has declined the fix', and reopens the bug. 
 
  * In case of a shared InspIRCd & Unreal4 issue where InspIRCd fixes it upstream first, set 'U4: Need for upstream patch' to 'Upstream fixed it before us' and point out the bug report to Committers which will then sync with upstream and resolve with information on which revision the sync was.

  * Upon bug resolving: If bug QA field is 'QA has accepted the fix', and 'U4: Upstream notification of bug' is set to 'Shared InspIRCd & Unreal4 issue reported by QA' and 'U4: Need for upstream patch' is 'Upstream patch needed', QA submits relevant information for InspIRCd to fix the issue (revision patches/urls), and sets 'U4: Need for upstream patch' to 'Upstream patch sent'. InspIRCd will then either decline (mark as 'Upstream patch declined') or accept - in this case in next sync there will be a patch that is already patched - or some edits done by InspIRCd team, which will then be corrected in Unreal4 as well.

==== Committers work ====
  * Upon bug confirmation: Committer fixes based on this information, 'assigned' to himself. When bug is fixed committer 'resolves' bug, comments in bug notes and updates what version it was fixed in and what revision.

  * Upon bug confirmation: Commiters perform mentorship through assigning the bug to themselves, and setting the 'U4: Contributor working on this field' to the nickname on bugtracker of the contributor and guide the contributor through the process.

  * Upon bug resolving by committer, sets QA field to "Fixed by developer, needs QA testing".

  * Upon bug resolving by committer, if 'U4: Upstream notification of bug' field is 'Shared InspIRCd & Unreal4 issue reported by QA', 'U4: Need for upstream patch' field is set to 'Upstream patch needed'

  * Upon bug reopening by QA, committer tries to fix the bug properly this time, and sets QA field to 'Fixed by developer, needs QA testing'


==== Global filters of interest for QA: ====

  * Unreal4 QA Unconfirmed- Bugs for 4.0 between "new" and "confirmed" (confirmed not included) - RSS: http://bugs.unrealircd.org/issues_rss.php?project_id=2&filter_id=1001
  * Unreal4 QA Needs Testing - Bugs for 4.0 marked "Fixed by developer, needs QA testing". RSS: http://bugs.unrealircd.org/issues_rss.php?project_id=2&filter_id=992
  * Unreal4 Upstream TODO - Bugs for 4.0 that are marked "QA has accepted the fix" and is marked Upstream patch needed, RSS: http://bugs.unrealircd.org/issues_rss.php?project_id=2&filter_id=993
  

==== Global filters of interest for developers ====
  * Unreal4 Confirmed Actual bugs (Doesn't include feature bugs): RSS: http://bugs.unrealircd.org/issues_rss.php?project_id=2&filter_id=1003 
  * Unreal4 Confirmed bugs: (Includes feature bugs): RSS: http://bugs.unrealircd.org/issues_rss.php?project_id=2&filter_id=1000
  * Unreal4 Features to work on: (Feature bugs only): RSS: http://bugs.unrealircd.org/issues_rss.php?project_id=2&filter_id=1004
  * Unreal4 QA Unconfirmed- Bugs for 4.0 between "new" and "confirmed" (confirmed not included) - RSS: http://bugs.unrealircd.org/issues_rss.php?project_id=2&filter_id=1001