diff options
Diffstat (limited to 'doc/release_policy.rfc.txt')
-rw-r--r-- | doc/release_policy.rfc.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/release_policy.rfc.txt b/doc/release_policy.rfc.txt index 8fd89f73c..41c98ec93 100644 --- a/doc/release_policy.rfc.txt +++ b/doc/release_policy.rfc.txt | |||
@@ -42,7 +42,7 @@ document the current release model: | |||
42 | mostly we rather explicitly declare certain bugs as "not critical") | 42 | mostly we rather explicitly declare certain bugs as "not critical") |
43 | - Whenever API changes happen the person making that changes should update | 43 | - Whenever API changes happen the person making that changes should update |
44 | dependencies or at least work with people who hack on the dependencies to | 44 | dependencies or at least work with people who hack on the dependencies to |
45 | cooridnate the adjustments | 45 | coordinate the adjustments |
46 | o buildbots are happy (if running) | 46 | o buildbots are happy (if running) |
47 | o static analysis is happy (if available, false-positives => ignore) | 47 | o static analysis is happy (if available, false-positives => ignore) |
48 | o documentation is reasonably up-to-date | 48 | o documentation is reasonably up-to-date |
@@ -57,7 +57,7 @@ For further information see: https://trunkbaseddevelopment.com/ | |||
57 | 57 | ||
58 | II. Evaluation Criteria | 58 | II. Evaluation Criteria |
59 | ======================= | 59 | ======================= |
60 | (what are criterias to interprete 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) |
62 | 62 | ||
63 | III. Concerns (of team members) | 63 | III. Concerns (of team members) |
@@ -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 stucked | 77 | missing releases which we feld 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 |
@@ -125,7 +125,7 @@ leaves of the dependency graph, that is great. However, occasionally | |||
125 | there are architectural changes. Not of the type where the graph | 125 | there are architectural changes. Not of the type where the graph |
126 | changes, but where key API assumptions change. We recently had one for | 126 | changes, but where key API assumptions change. We recently had one for |
127 | the GNU Name System with the dropping of ".gnu". Before, CADET | 127 | the GNU Name System with the dropping of ".gnu". Before, CADET |
128 | changed the semantics and paramter for 'port'. In the future, CORE | 128 | changed the semantics and parameter for 'port'. In the future, CORE |
129 | will introduce protocol versioning. Whenever such a change happens, | 129 | will introduce protocol versioning. Whenever such a change happens, |
130 | it usually falls upon the person making that change to update | 130 | it usually falls upon the person making that change to update |
131 | dependencies as well (or at least to work with people who hack on the | 131 | dependencies as well (or at least to work with people who hack on the |
@@ -175,7 +175,7 @@ Note that none of this really adds up to a "release policy". | |||
175 | V. Previous Versions | 175 | V. Previous Versions |
176 | ==================== | 176 | ==================== |
177 | (if we found some flaws in the solution, and we want to change the | 177 | (if we found some flaws in the solution, and we want to change the |
178 | release policy, we document the old ones here als previous versions. | 178 | release policy, we document the old ones here as previous versions. |
179 | the goal is establish a learn process.) | 179 | the goal is establish a learn process.) |
180 | 180 | ||
181 | IV. References | 181 | IV. References |