| 1 |
From: Sebastian Luther <SebastianLuther@×××.de> |
| 2 |
|
| 3 |
--- |
| 4 |
DEVELOPING | 28 ++++++++++++++++++++++++++++ |
| 5 |
1 file changed, 28 insertions(+) |
| 6 |
|
| 7 |
diff --git a/DEVELOPING b/DEVELOPING |
| 8 |
index a2c9ae1..7a97d3d 100644 |
| 9 |
--- a/DEVELOPING |
| 10 |
+++ b/DEVELOPING |
| 11 |
@@ -161,6 +161,34 @@ somewhat annoying because the import line needs to be modified when functions |
| 12 |
are needed and often unused functions are left in the import line until someone |
| 13 |
comes along with a linter to clean up (does not happen often). |
| 14 |
|
| 15 |
+Bugzilla |
| 16 |
+-------- |
| 17 |
+ |
| 18 |
+There always exists a tracker bug, named: |
| 19 |
+"[Tracker] sys-apps/portage-<next version>". |
| 20 |
+ |
| 21 |
+This bug is renamed from X.Y.Z to X.Y.Z+1 after a release, until |
| 22 |
+it gets closed when Y changes and a new one is opened. |
| 23 |
+ |
| 24 |
+Whenever a commit for a specific bug is made to the git repo, |
| 25 |
+the corresponding bug gets changed in the following ways: |
| 26 |
+* InVCS is added to Keywords |
| 27 |
+* The bug is marked as blocking the tracker for the next version |
| 28 |
+* A comment is added saying: This is fixed in git: <url to commit> |
| 29 |
+(note that the bug stays open) |
| 30 |
+ |
| 31 |
+After a release all open bugs blocking the tracker are closed |
| 32 |
+with the comment "This is fixed in <version>.". |
| 33 |
+ |
| 34 |
+For individual open bugs it is encouraged to set UNCONFIRMED, |
| 35 |
+CONFIRMED or IN_PROGESS as appropriate. |
| 36 |
+ |
| 37 |
+There are a number of bugs named "[TRACKER] *" that collect bugs |
| 38 |
+for specific topics. Confirmed bugs should be marked as blocking |
| 39 |
+these tracker bugs if appropriate. |
| 40 |
+ |
| 41 |
+It is encouraged to set the alias field for frequently used bugs. |
| 42 |
+ |
| 43 |
|
| 44 |
Releases |
| 45 |
-------- |
| 46 |
-- |
| 47 |
1.8.3.2 |
Archives