diff options
Diffstat (limited to 'doc/release_policy.rfc.txt')
-rw-r--r-- | doc/release_policy.rfc.txt | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/release_policy.rfc.txt b/doc/release_policy.rfc.txt index 41c98ec93..e13e72f43 100644 --- a/doc/release_policy.rfc.txt +++ b/doc/release_policy.rfc.txt | |||
@@ -7,17 +7,17 @@ social process in order to find a decision in a cooperativ and common | |||
7 | way. | 7 | way. |
8 | 8 | ||
9 | 9 | ||
10 | I. Driver | 10 | I. Driver |
11 | ========= | 11 | ========= |
12 | (What is the problem and what solution did we find?) | 12 | (What is the problem and what solution did we find?) |
13 | 13 | ||
14 | In the past it was sometimes unclear when and how the community would reach its | 14 | In the past it was sometimes unclear when and how the community would reach its |
15 | next release. Members were lacking in orientation and felt demotivated. | 15 | next release. Members were lacking in orientation and felt demotivated. |
16 | 16 | ||
17 | Another minor concern not yet analysed in depth was the expectation to show the | 17 | Another minor concern not yet analysed in depth was the expectation to show the |
18 | public that the GNUnet project is still active and making progress. With an old | 18 | public that the GNUnet project is still active and making progress. With an old |
19 | release distributed by popular linux distributions it was hard to showcase | 19 | release distributed by popular linux distributions it was hard to showcase |
20 | people the GNUnet features and encourage to participate in the project. | 20 | people the GNUnet features and encourage to participate in the project. |
21 | 21 | ||
22 | To show people how the GNUnet project is releasing its software we hereby | 22 | To show people how the GNUnet project is releasing its software we hereby |
23 | document the current release model: | 23 | document the current release model: |
@@ -55,7 +55,7 @@ document the current release model: | |||
55 | 55 | ||
56 | For further information see: https://trunkbaseddevelopment.com/ | 56 | For further information see: https://trunkbaseddevelopment.com/ |
57 | 57 | ||
58 | II. Evaluation Criteria | 58 | II. Evaluation Criteria |
59 | ======================= | 59 | ======================= |
60 | (what are criteria to interpret the results as success if we review | 60 | (what are criteria to interpret the results as success if we review |
61 | the problem and solution after a year or so) | 61 | the problem and solution after a year or so) |
@@ -74,7 +74,7 @@ code. I don't have a magic bullet to motivate you to write more tests, | |||
74 | or to improve existing tests. -CG | 74 | or to improve existing tests. -CG |
75 | 75 | ||
76 | Your argument is good. Two or three of us thought that the problem is about | 76 | Your argument is good. Two or three of us thought that the problem is about |
77 | missing releases which we feld demotivating. We thought, we were stuck | 77 | missing releases which we felt demotivating. We thought, we were stuck |
78 | somewhere. But as you state, it is us not doing the necessary work. What I | 78 | somewhere. But as you state, it is us not doing the necessary work. What I |
79 | still find useful is to document the release process. In consequence I | 79 | still find useful is to document the release process. In consequence I |
80 | changed the problem statement. -xrs | 80 | changed the problem statement. -xrs |
@@ -106,7 +106,7 @@ for improving that situation). -CG | |||
106 | With resprect to changes kept in branches the reason why I personally keep | 106 | With resprect to changes kept in branches the reason why I personally keep |
107 | changes back is because it takes very long for me to get something really | 107 | changes back is because it takes very long for me to get something really |
108 | working in C. Before that I either not worth it or I don't want to blame | 108 | working in C. Before that I either not worth it or I don't want to blame |
109 | other before not being sure it's not my fault. | 109 | other before not being sure it's not my fault. |
110 | 110 | ||
111 | Can we track branches? Can we write a little cronjob that checks for branches | 111 | Can we track branches? Can we write a little cronjob that checks for branches |
112 | that are to long undercover with the aim to recommend the responsible person | 112 | that are to long undercover with the aim to recommend the responsible person |
@@ -137,7 +137,7 @@ rewrites are happening, it is important to minimize the number of | |||
137 | branches. -CG | 137 | branches. -CG |
138 | 138 | ||
139 | Thank you for clarifying. I added the API aspect above. -xrs | 139 | Thank you for clarifying. I added the API aspect above. -xrs |
140 | 140 | ||
141 | 141 | ||
142 | IV. Doing | 142 | IV. Doing |
143 | ========= | 143 | ========= |
@@ -153,7 +153,7 @@ Let me list what I think needs doing: | |||
153 | 2) A culture of fixing "other people"'s bugs: test case failures, | 153 | 2) A culture of fixing "other people"'s bugs: test case failures, |
154 | portability issues, Mantis reports, all the non-sexy | 154 | portability issues, Mantis reports, all the non-sexy |
155 | stuff. Not the 'psycstore' was written by tg, so no | 155 | stuff. Not the 'psycstore' was written by tg, so no |
156 | need for !tg to try to fix it, or the "I use sqlite, | 156 | need for !tg to try to fix it, or the "I use sqlite, |
157 | why should I bother with postgres?"-crap I have heard | 157 | why should I bother with postgres?"-crap I have heard |
158 | too often. | 158 | too often. |
159 | 3) Improving test cases: better code coverage, more corner | 159 | 3) Improving test cases: better code coverage, more corner |