This is idea brainstorming for a community plugin for releasing cookbooks per Opscode's current process. This would replace the functionality of the "cookbook site share" plugin that is built into Chef, as I believe the cookbook site plugins should use "community" rather than "cookbook site" and be a separate plugin instead of built into Chef and tied to its release cycle.
knife community release COOKBOOK VERSION
Assumes that the repository is release ready, e.g., the current HEAD is the commit that should be released, CHANGELOG is updated already, etc.
- sets metadata version to the specified VERSION
- makes a git commit with the release VERSION in the metadata
- creates a git tag with the bare version, e.g. "1.0.1" not "v1.0.2"
- pushes to the opscode (or other upstream as apropos) master branch, takes --remote argument as alternate, and pushes git tags