Update release notes and maintenance stuff.

MAINTENANCE.md

@@ -4,8 +4,14 @@ Be sure that JAVA_HOME is set. On the Mac:
 
         export JAVA_HOME=`/usr/libexec/java_home -v 1.7`
 
+Then run this:
+
 	mvn -DautoVersionSubmodules=true release:prepare
 	mvn release:perform
+	pushd target/checkout/npm-package/target/trireme-npm-x.x.x-bin
+	npm publish
+        popd
+	(Verify on oss.sonatype.com that it is all OK.)
 	mvn release:clean
 
 What this does:
@@ -18,6 +24,7 @@ What this does:
 6) Checks out the tag in a temporary directory
 7) Builds there (without running tests)
 8) Uploads the artifacts to the repo
+9) Publishes the latest "trireme" to NPM.
 
 ** If it doesn't work
 
@@ -43,7 +50,11 @@ labdt1 on our internal network). You will need to have
 	  </servers>
 	</settings>
 
-If the "deploy" task fails part way, then some deployment tasks will return
+If the "deploy" task fails part way, you can cd to "target/checkout/",
+then to the specific modules that failed, and "npm publish"
+manually. 
+
+Sometimes, deployment tasks will return
 a "409" (conflict) status. You can fix this by using the Archiva web app to
 manually delete the artifacts and try again. I'm not sure of a better way
 to do this.
@@ -64,6 +75,12 @@ Apparently this can be automated, but it has not been automated yet.
 Sometimes the validation step fails, so you can't do the release. This
 might happen if a file upload breaks.
 
+The best thing to do in this case is to go to "target/checkout" 
+and "npm publish" the individual modules.
+
+However, if you did "mvn release:cleanup" first then you might 
+need to rebuild the release manually.
+
 In that case, you can:
 
 Get the tag that you pushed during release:prepare:

README.md

@@ -160,7 +160,7 @@ although it may not necessarily pass all the node.js tests.
   <tr><td>readline</td><td>Partial</td><td>node.js</td></tr>
   <tr><td>repl</td><td>Not Supported</td><td>node.js</td></tr>
   <tr><td>stream</td><td>Complete</td><td>node.js</td></tr>
-  <tr><td>string_decoder</td><td>Complete</td><td>Trireme</td></tr>
+  <tr><td>string_decoder</td><td>Complete</td><td>node.js</td></tr>
   <tr><td>timers</td><td>Complete</td><td>node.js + Trireme</td></tr>
   <tr><td>tls</td><td>Complete but See Notes</td><td>Trireme</td></tr>
   <tr><td>tty</td><td>Complete</td><td>Trireme</td></tr>

RELEASE-NOTES.md

@@ -1,3 +1,18 @@
+* 0.8.4 5-Dec-2014:
+
+This is a bug fix for a few important bugs. The next release may include some more refactoring.
+
+* [Issue 90](https://github.com/apigee/trireme/issues/90) Make "attachments" to the HTTP adapter's request
+object non-enumerable so that they don't blow up util.inspect.
+* [Issue 91](https://github.com/apigee/trireme/issues/91) Support case-insensitive retrieval of environment
+variables, like Windows. This makes variables like "Path" work on Windows.
+* [Issue 92](https://github.com/apigee/trireme/issues/92) Fix the string encoding and decoding mechanisms so
+that characters that are not valid for the current character set are converted into a "replacement" character
+rather than causing string encoding to stop.
+* [Issue 94](https://github.com/apigee/trireme/issues/94) Repeated HTTP requests sometimes fail because
+of problems with resetting the state of the HTTP parser that the "http" module tries to cache. (Said caching
+may be important with regular Node, but in Trireme is has no performance benefit.)
+
 * 0.8.3 15-Oct-2014:
 
 * Fix the error that happens when "dlopen" cannot find load a native code module. This bug was causing