[gentoo-portage-dev] [PATCH] Document bugzilla workflow

[SebastianLuther@gmx.de]

From: Sebastian Luther <SebastianLuther@gmx.de>

---
 DEVELOPING | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/DEVELOPING b/DEVELOPING
index a2c9ae1..7a97d3d 100644
--- a/DEVELOPING
+++ b/DEVELOPING
@@ -161,6 +161,34 @@ somewhat annoying because the import line needs to be modified when functions
 are needed and often unused functions are left in the import line until someone
 comes along with a linter to clean up (does not happen often).
 
+Bugzilla
+--------
+
+There always exists a tracker bug, named:
+"[Tracker] sys-apps/portage-<next version>".
+
+This bug is renamed from X.Y.Z to X.Y.Z+1 after a release, until
+it gets closed when Y changes and a new one is opened.
+
+Whenever a commit for a specific bug is made to the git repo,
+the corresponding bug gets changed in the following ways:
+* InVCS is added to Keywords
+* The bug is marked as blocking the tracker for the next version
+* A comment is added saying: This is fixed in git: <url to commit>
+(note that the bug stays open)
+
+After a release all open bugs blocking the tracker are closed
+with the comment "This is fixed in <version>.".
+
+For individual open bugs it is encouraged to set UNCONFIRMED,
+CONFIRMED or IN_PROGESS as appropriate.
+
+There are a number of bugs named "[TRACKER] *" that collect bugs
+for specific topics. Confirmed bugs should be marked as blocking
+these tracker bugs if appropriate.
+
+It is encouraged to set the alias field for frequently used bugs.
+
 
 Releases
 --------
-- 
1.8.3.2