Browse Source

Changes versioning explanation in preperation of 1.2 release.

Coming back to a minor bump model if new icons are added.
Julien Deswaef 5 years ago
parent
commit
584ab41048
1 changed files with 2 additions and 2 deletions
  1. 2 2
      README.md

+ 2 - 2
README.md

@@ -45,8 +45,8 @@ with the following format:
 And constructed with the following guidelines:
 And constructed with the following guidelines:
 
 
 * Breaking backward compatibility bumps the major (and resets the minor and patch)
 * Breaking backward compatibility bumps the major (and resets the minor and patch)
-* Big changes, without breaking backward compatibility, bumps the minor (and resets the patch)
-* Bug fixes, small adaptations, adding a few icons and misc changes bumps the patch
+* New additions, including new icons, without breaking backward compatibility, bumps the minor (and resets the patch)
+* Bug fixes, changes to brand logos, and misc changes bumps the patch
 * The fork started from FontAwesome 4.7 (last commit by Dave is [bdfa9823](https://github.com/ForkAwesome/Fork-Awesome/commits/master?after=b0bc8f6fb74e05c987ef7ce1525cd3ab8390a1c3+69)).
 * The fork started from FontAwesome 4.7 (last commit by Dave is [bdfa9823](https://github.com/ForkAwesome/Fork-Awesome/commits/master?after=b0bc8f6fb74e05c987ef7ce1525cd3ab8390a1c3+69)).
 * The project starts at version 1.0.0. All references to versions before the fork are named 0.4.7
 * The project starts at version 1.0.0. All references to versions before the fork are named 0.4.7