Select 4.0-devel for 4.0 bugs, and the correct version for 3.2.* bugs.
Set severity field to 'feature'
From the CVS checkout root,
cvs diff -u > patchname.patch
From the SVN checkout root,
svn diff > patchname.patch
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.
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.
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.
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.
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 reopening by QA, committer tries to fix the bug properly this time, and sets QA field to 'Fixed by developer, needs QA testing'