update release procedure with my current findings

Release-Procedure.md

@@ -1,5 +1,8 @@
 This document is a work in progress.  When it is finalized, it should be included as a doc within the repository itself.
 
+### Run unit tests
+Start with running unit tests in IE9, IE10, IE11, latest Safari, latest Chrome and latest Firefox and make sure all tests pass before the release process is started.
+
 ### Create a release branch
 
 The release process involves a couple changes to the repository: updating the version number in package.json and adding a changelog.  In order to make these release-related changes, create a branch in your ol3 clone.  Note that all the examples below use 3.1.0 as the release version (and 3.0.0 as the previous release).  You'll want to use the appropriate version numbers for the release you're working toward.
@@ -85,6 +88,8 @@ Publish the release artifacts (examples and source) on the website.  In a workin
     # publish
     treeish=v3.1.0 npm run deploy
 
+If you run into ```Warning: ENFILE: file table overflow```` check out http://superuser.com/questions/433746/is-there-a-fix-for-the-too-many-open-files-in-system-error-on-os-x-10-7-1
+
 ### Create release page and post archive for download
 
 Create an archive from the artifacts created by the `npm run deploy` step above.  This includes the documentation and source.