Skip to content

Commit

Permalink
bower.json: Package this lesson for Bower
Browse files Browse the repository at this point in the history
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
wking committed Mar 24, 2015
1 parent 027ea0d commit 4720be5
Showing 1 changed file with 31 additions and 0 deletions.
31 changes: 31 additions & 0 deletions bower.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
{
"name": "awk-lesson",
"description": "An hour-long lesson on text Parsing with `awk`, `sed` and `paste`",
"version": "0.1.0",
"main": "lesson.md",
"license": "MIT",
"keywords": [
"lesson",
"mozilla-science-lab",
"study-group",
"awk",
"sed",
"paste"
],
"authors": [
{
"name": "Kathi Unglert",
"homepage": "http://volcano-diaries.blogspot.com/"
},
{
"name": "Bill Mills",
"email": "[email protected]",
"homepage": "https://twitter.com/billdoesphysics"
}
],
"homepage": "https://github.com/BillMills/awk-lesson",
"repository": {
"type": "git",
"url": "git://github.com/BillMills/awk-lesson.git"
}
}

0 comments on commit 4720be5

Please sign in to comment.