Updated changelog and readme.

Author: DanielKeep

CHANGELOG.md

@@ -1,4 +1,10 @@
 
+# v0.2.8
+
+**Changed:**
+
+* Implemented work-around for [issue 50](https://github.com/DanielKeep/cargo-script/issues/50).  See the section in the `README` on known issues.
+
 # v0.2.7
 
 **New:**

README.md

@@ -27,6 +27,7 @@ Table of contents:
   - [Stream Filters](#filters)
   - [Environment Variables](#env-vars)
   - [Templates](#templates)
+- [Known Issues](#issues)
 - [License](#license)
   - [Contribution](#contribution)
 
@@ -265,6 +266,15 @@ $ cargo script -t grabbag -e "mem::size_of::<Box<Read>>()"
 
 In addition, there are three built-in templates: `expr`, `loop`, and `loop-count`.  These are used for the `--expr`, `--loop`, and `--loop --count` invocation forms.  They can be overridden by placing templates with the same name in the template folder.  If you have *not* overridden them, you can dump the contents of these built-in templates using the `templates dump` command noted above.
 
+<a name="issues"></a>
+## Known Issues
+
+### [Issue #50](https://github.com/DanielKeep/cargo-script/issues/50)
+
+There is a problem on Windows where `cargo-script` can hang when asking Cargo for the path to a package's compiled executable.  `cargo-script` currently works around this by using an older heuristic to guess this path on affected versions.  This can, however, lead to `cargo-script` being unable to correctly locate a compiled executable.
+
+If this is a problem, `cargo-script` can be instructed to use the accurate-but-buggy approach by setting the `CARGO_SCRIPT_IGNORE_ISSUE_50` environment variable to any non-empty string.
+
 <a name="license"></a>
 ## License