Update info around development branches

Author: hollasch

CONTRIBUTING.md

@@ -27,7 +27,9 @@ raytracing.github.io/      # Repository root
 ```
 
 The latest official release can be found in the `master` branch. All ongoing development work (and
-all of the latest changes) will be in the `development` branch.
+all of the latest changes) will be in the `dev-patch`, `dev-minor`, and `dev-major` branches. The
+appropriate target branch for any pull requests you want to make will be determined in the
+associated issue first (all PRs should have an associated issue).
 
 
 Issues
@@ -49,17 +51,18 @@ Pull Requests
 --------------
 To contribute a change to the project, please follow these steps:
 
-  1. [Create a GitHub issue](https://github.com/RayTracing/raytracing.github.io/issues)
+  1. [Create a GitHub issue](https://github.com/RayTracing/raytracing.github.io/issues).
 
   2. Participate in the discussion as needed. We'll ensure that the work doesn't conflict with or
-     duplicate other work planned or in progress, and makes sense for the next release.
+     duplicate other work planned or in progress, and decide which development branch is correct
+     for the release type and release schedule.
 
-  3. Create your changes in a feature branch (or fork) from the `development` branch (_not_ from
-     `master`).
+  3. Create your changes in a feature branch (or fork) from the assigned development branch
+     (probably `dev-patch`, `dev-minor`, `dev-major`, or `future`).
 
   4. Follow existing code style.
 
-  5. When ready, create a pull request and assign it to "rt-contributors".
+  5. When ready, create a pull request and request a review from "rt-contributors".
 
 New to GitHub? We'll walk you through the process above. Just mention that you'd like a little
 guidance in the proposal issue.

README.md

@@ -33,8 +33,7 @@ of changes to areas of the book that have given readers difficulties. Enjoy!
 Branches
 ---------
 The `master` branch contains the code at latest release. All ongoing development, with all of the
-latest changes, can be found in the `development` branch. If you have issues to file, you may want
-to check to see if they're still present in the `development` branch.
+latest changes, can be found in the `dev-patch`, `dev-minor`, and `dev-major` branches.
 
 
 Downloading The Source Code

index.html

@@ -69,14 +69,17 @@ <h1 id='source'>Source Code</h1>
 
   <h1 id='issues'>Issues</h1>
 
-  <p>You can browse book suggestions and errors in the
-  <a href="https://github.com/RayTracing/raytracing.github.io/issues">GitHub issues database</a>. If you have a
-  suggestion or believe you've found an error, please check these issues first (including closed issues) to ensure that
-  it hasn't already been reported. If it hasn't, please create a new entry, describing the issue, book, specific
+  <p>You can browse book suggestions and errors in
+  <a href="https://github.com/RayTracing/raytracing.github.io/issues">GitHub issues</a>. If you have a suggestion or
+  believe you've found an error, please check these issues first (including closed ones) to ensure that it hasn't
+  already been reported. If it hasn't, please create a new entry, describing the problem, book or source file, location,
+  and whatever other information would be helpful in understanding why you think it's a problem. If possible, include
+  ideas about what you think the fix should look like.
 
 
   <h1 id='contributing'>Contributing</h1>
-  <p>Interested in helping out? Please read the guidelines in the <a href="https://github.com/RayTracing/raytracing.github.io/blob/master/CONTRIBUTING.md">CONTRIBUTING.md</a> document
+  <p>Interested in helping out? Please read the guidelines in the
+  <a href="https://github.com/RayTracing/raytracing.github.io/blob/master/CONTRIBUTING.md">CONTRIBUTING.md</a> document
   first. <em>Pull requests without associated issues, or submitted without coordination, are highly likely to be
   rejected.</em>