Official Update Process

1. When a feature is ready to go live, a pull-request is submitted. Small hotfixes can be performed on the master branch - larger ones it would be good if a new branch were created, and pull request submitted. This allows others to review the updates to make sure they're stable and ready to go live, as well as offer some code improvements.
2. That pull-request gets merged into the master branch. The Version number is incremented in the manifest file.
3. a Release is marked on github along with the changes that were performed.
4. That release's zip file gets uploaded by @jonmclaren to the Google Chrome Web Store.

Down the road we want to automate step 4 so it's not reliant upon someone manually updating it.