fix(create): copy correct folder, use gulp instead of shell
fix(bowerCheck): prevent linux errors by installing with --allow-root by default
fix(bowerCheck): use gulp color logger
feat(depCheck): add task that checks whether required binaries are installed
Release 0.6.0
feat(angus.js): check for config file
feat(angus.js): add version information when command is run
fix(depCheck): no need for compass, only sass
Release 0.7.0
fix(jsLib): only copy JS libraries if there are any, otherwise gulp fails with an empty stream
fix(bowerCheck): don't ask the user what version works best, always use latest

When Bower asks the user which version it needs to install, it's a question which is not the user's problem. It's unnecessary, gives headaches and should be removed. The goal of Angus is to give you a smooth experience, and questions like these mess that up. Read http://www.joelonsoftware.com/uibook/chapters/fog0000000059.html
Strict versioning isn't as important for bower as it is for npm, which deals with a lot more critical things like disk latency, networking and most of all security. If something on the client doesn't work, you will notice it when you open up the browser. Use the strict versioning syntax <package>@<version> in angus.config.js if you're paranoid.
feat(jsApp): don't include end-to-end tests (*.e2e.*.js syntax)
feat(jsApp): don't include unit tests (*.unit.*.js syntax)
feat(bower): ability to copy bower assets into app assets
feat(filesNeeded): allow globs
feat(bower): ability to symlink local app folders
feat(docs): update README
Release 0.8.0
fix(npmignore): ignore config.json
Update README.md