aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2021-04-23 23:58:12 +0200
committerChristian Grothoff <christian@grothoff.org>2021-04-23 23:58:34 +0200
commitf630c5a675ca37467b5fba9a3dd41044381ac6ce (patch)
tree113686bec5c58182de320db503f86fa16f2c8c05 /doc
parent11f5b0148a8343c776b2562494840ad2963959fb (diff)
downloadgnunet-f630c5a675ca37467b5fba9a3dd41044381ac6ce.tar.gz
gnunet-f630c5a675ca37467b5fba9a3dd41044381ac6ce.zip
-fix typos
Diffstat (limited to 'doc')
-rw-r--r--doc/index.html2
-rw-r--r--doc/release_policy.rfc.txt10
2 files changed, 6 insertions, 6 deletions
diff --git a/doc/index.html b/doc/index.html
index 93c0e7d9e..bf8683780 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -2,7 +2,7 @@
2 <head> 2 <head>
3 <title>GNUnet - GNUnet Manuals and Handbooks</title> 3 <title>GNUnet - GNUnet Manuals and Handbooks</title>
4 <meta charset="utf-8"> 4 <meta charset="utf-8">
5 <meta name="keywords" content="gnunet,GNUnet,Manual,Manuals,preview,developer-preview,inofficial,GNU"> 5 <meta name="keywords" content="gnunet,GNUnet,Manual,Manuals,preview,developer-preview,unofficial,GNU">
6 <meta name="description" content="The GNUnet Manuals"> 6 <meta name="description" content="The GNUnet Manuals">
7 <link href="style.css" rel="stylesheet"> 7 <link href="style.css" rel="stylesheet">
8 <meta name="viewport" content="width=device-width, initial-scale=1"> 8 <meta name="viewport" content="width=device-width, initial-scale=1">
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
58II. Evaluation Criteria 58II. 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
61the problem and solution after a year or so) 61the problem and solution after a year or so)
62 62
63III. Concerns (of team members) 63III. Concerns (of team members)
@@ -74,7 +74,7 @@ code. I don't have a magic bullet to motivate you to write more tests,
74or to improve existing tests. -CG 74or 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
125there are architectural changes. Not of the type where the graph 125there are architectural changes. Not of the type where the graph
126changes, but where key API assumptions change. We recently had one for 126changes, but where key API assumptions change. We recently had one for
127the GNU Name System with the dropping of ".gnu". Before, CADET 127the GNU Name System with the dropping of ".gnu". Before, CADET
128changed the semantics and paramter for 'port'. In the future, CORE 128changed the semantics and parameter for 'port'. In the future, CORE
129will introduce protocol versioning. Whenever such a change happens, 129will introduce protocol versioning. Whenever such a change happens,
130it usually falls upon the person making that change to update 130it usually falls upon the person making that change to update
131dependencies as well (or at least to work with people who hack on the 131dependencies 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".
175V. Previous Versions 175V. 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
178release policy, we document the old ones here als previous versions. 178release policy, we document the old ones here as previous versions.
179the goal is establish a learn process.) 179the goal is establish a learn process.)
180 180
181IV. References 181IV. References