projects
/
linux-libre-firmware.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Add missing word "the" to the CONTRIBUTING guide
[linux-libre-firmware.git]
/
CONTRIBUTING
diff --git
a/CONTRIBUTING
b/CONTRIBUTING
index 29e647398ab2e978d2b6af061f89dc82b0bdf97f..94523be23ce0a61cb4d2b0a2a88721cc7cbb3292 100644
(file)
--- a/
CONTRIBUTING
+++ b/
CONTRIBUTING
@@
-58,8
+58,8
@@
between versions.
Every change, no matter how well-intentioned, introduces the potential
for unexpected problems. For this reason changes on a release branch
Every change, no matter how well-intentioned, introduces the potential
for unexpected problems. For this reason changes on a release branch
-are more stringent, as opposed to
"anything can change" philosophy of
-the master branch.
+are more stringent, as opposed to
the "anything can change"
+
philosophy of
the master branch.
There are only two types of changes that can be made to a release
branch:
There are only two types of changes that can be made to a release
branch:
@@
-74,6
+74,9
@@
Updates for a released version involve adding a third point to the
version number: 1.2.1, etc. and this third point is incremented by 1
with every release (1.2.2, 1.2.3, etc.)
version number: 1.2.1, etc. and this third point is incremented by 1
with every release (1.2.2, 1.2.3, etc.)
+There is no timetable for releases: New versions are released when
+they're ready. Updates to release branches are made as needed.
+
Licensing
---------
Licensing
---------