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:
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
---------
-You can redistribute it and/or modify this file under the terms of the
+You can redistribute and/or modify this file under the terms of the
GNU General Public License as published by the Free Software
Foundation, either version 3 of the License, or (at your option) any
later version.