fix(scripts): Make minor fixes to release scripts (and docs) (#164)

- Change wording in pre-release script to omit info regarding committing
  a changelog. This is done within a post-release step.
- Make scripts/post-release executable
- Add a note about adding the correct publishConfig to new packages so
  that lerna can auto-published scoped packages to npm

[ci skip]

Author: traviskaufman

docs/authoring-components.md

@@ -484,6 +484,16 @@ demos
 When contributing a new component, we encourage you to look at existing components to get a better
 sense of our conventions. Your new component should "blend in" with all existing components.
 
+Additionally, all new components require the following within their `package.json`:
+
+```
+"publishConfig": {
+  "access": "public"
+}
+```
+
+This is needed so that lerna will be able to automatically publish new scoped packages.
+
 ### License Stanzas
 
 We are required to put the following at the _top_ of _every source code file_, including tests,

scripts/post-release.sh

@@ -38,7 +38,7 @@ log "Determining package versions..."
 node scripts/determine-pkg-versions.js
 echo ""
 
-log "Pre-release steps done! You should now commit the changelog and then run " \
+log "Pre-release steps done! You should now run " \
     "\$(npm bin)/lerna publish, followed by ./scripts/post-release.sh"
 log "Please use the package versions specified above to increment the different package versions " \
     "When prompted by lerna. Or, override those versions if need be."