Updated the readme to remove references to the 'bugfix' branch

Author: bvarner

README.md

@@ -78,8 +78,8 @@ One common stumbling block for teams adjusting to gitflow with Maven projects is
 In practice, the Maven versions should:
 
  * Be synchronized with release branch and hotfix branch names.
- * Never be -SNAPSHOT in the master branch, release, hotfix, or bugfix branches.
- * Always be -SNAPSHOT in the development or feature branches.
+ * Never be -SNAPSHOT in the master branch, release, or hotfix branches.
+ * Always be -SNAPSHOT in the development branch.
  * Be irrelevant if there's no git branch resolvable from your environment.
 
 The `enforce-versions` goal asserts these semantics when it can resolve the `gitBranchExpression`.
@@ -96,7 +96,6 @@ The following properties change the behavior of this goal:
 | masterBranchPattern  | origin/master | No | Regex. When matched, signals the master branch is being built. Note the lack of a subgroup. |
 | releaseBranchPattern | origin/release/(.*) | No | Regex. When matched, signals a release branch being built. Subgroup 1, if present, must match the Maven project version. |
 | hotfixBranchPattern  | origin/hotfix/(.*) | No | Regex. When matched, signals a hotfix branch is being built. Subgroup 1, if present, must match the Maven project version. |
-| bugfixBranchPattern  | origin/bugfix/.* | No | Regex. When matched, signals a bugfix branch is being built. Note the lack of a subgroup. |
 | developmentBranchPattern | origin/development | Yes | Regex. When matched, signals a development branch is being built. Note the lack of a subgroup. |
 
 ## Goal: `retarget-deploy` (Branch Specific Deploy Targets & Staging)
@@ -240,7 +239,6 @@ The following table describes the git branch expression -> repository used for r
 | masterBranchPattern   | release    |
 | releaseBranchPattern  | stage      |
 | hotfixBranchPattern   | stage      |
-| bugfixBranchPattern   | stage      |
 | developmentBranchPattern | snapshots | 
 | All Others            | local      |