Changes between Version 14 and Version 15 of StartModWorkflow

Timestamp:

Dec 13, 2013, 10:06:31 PM (9 years ago)

Author:

Beman Dawes

Comment:

--

StartModWorkflow

@@ -39 +39 @@
 
 Individual Boost libraries are free to choose their own release numbers, and these library release numbers are normally unrelated to the release numbers for the Boost super-project. The recommended release naming convention is the traditional three unsigned integers separated by periods (I.E. 1.2.3) where:
- * The first integer is the major version number, with each major version, with 0 being used for initial development and 1 for the first production-usable version.
+ * The first integer is the major version number, with each major version, with 0 being used for initial development and 1 for the first production-usable version. A change in version number is recommended when there are breaking changes.
  * The middle integer is the release number, reset to 0 with each version update and otherwise increasing monotonically.
  * The last integer is the patch level, reset to 0 with each revision and otherwise increasing monotonically. A patch level greater than 1 indicates a so-called point releases, normally containing bug fixes but not new features.
@@ -55 +55 @@
 
 The usual culture with Git is to delete feature branches as soon as
-they are merged to some other branch.
+they are merged to some other branch, and is followed by Git Flow.
 This approach is also recommended for Boost developers.
 After all, the merged-to branch