Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bower.json: Package this lesson for Bower
Docs for bower.json are at [1,2]. Once this gets merged, you'll want to tag a 0.1.0 release: $ git tag -s -m 'version 0.1.0' v0.1.0 $ git push --tags and register the package with [3]: $ bower register awk-lesson git://github.com/BillMills/awk-lesson.git I'm starting with version 0.1.0 as recommended for semantic versioning [4]. [1]: http://bower.io/docs/creating-packages/#bowerjson [2]: https://github.com/bower/bower.json-spec [3]: http://bower.io/docs/creating-packages/#register [4]: http://semver.org/ How should I deal with revisions in the 0.y.z initial development phase? The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.
- Loading branch information