Show More
@@ -183,9 +183,11 b' mailing list. We aim at having all non-' | |||||
183 | one other core developer before pushing. Obvious non-controversial changes will |
|
183 | one other core developer before pushing. Obvious non-controversial changes will | |
184 | be handled more casually. |
|
184 | be handled more casually. | |
185 |
|
185 | |||
186 | For now we just have one official branch ("default") and will keep it so stable |
|
186 | There is a main development branch ("default") which is generally stable so that | |
187 |
|
|
187 | it can be (and is) used in production. There is also a "stable" branch that is | |
188 | elsewhere (for example in a pull request) until they are ready. |
|
188 | almost exclusively reserved for bug fixes or trivial changes. Experimental | |
|
189 | changes should live elsewhere (for example in a pull request) until they are | |||
|
190 | ready. | |||
189 |
|
191 | |||
190 | .. _coding-guidelines: |
|
192 | .. _coding-guidelines: | |
191 |
|
193 |
General Comments 0
You need to be logged in to leave comments.
Login now