search

nathansmith / unsemantic

Fluid grid for mobile, tablet, and desktop.
http://unsemantic.com
MIT License
1.38k stars 162 forks source link

Tag releases #53

Closed freefri closed 9 years ago

freefri commented 10 years ago

I think it will be nice if you start to use git tags. If you do so, people that is developing using unsemantic and bower can easily control the version they are using without having to set a commit hash, and allowing to take update minor releases like "1.2.*" This will avoid conflicts with new versions.

nathansmith commented 10 years ago

I didn't anticipate people wanting to use Unsemantic with Bower.

There's an open ticket for adding a bower.json file to the repo…

https://github.com/nathansmith/unsemantic/issues/48

I'm waiting for those who have posted to reply as to what the bower.json file should look like.

I personally haven't used Bower for anything, so I'm not sure what the file should include.

I am curious though, how are you using Unsemantic with Bower, without the a bower.json file?

freefri commented 10 years ago

You could have a look in here: http://bower.io/search/?q=unsemantic I dont know bower very deep but you can add any github project with bower. For example, adding the following to the Bower.json of my proyect I get unsemantic (the last version): "unsemantic": "latest"

If in your releases you add tags (and push them to github, see http://git-scm.com/book/en/Git-Basics-Tagging) I could get the versions I want.

i.e. you create a tag called "0.1.2" and then I can get this version of your repo with "unsemantic": "0.1.2". If later you decide to add the version "0.1.3" I wont get the update. But I could also add "unsemantic": "0.1.*" and then I will get "0.1.3" and if you add "0.2.1" I will still get "0.1.3" (have a look at https://github.com/bower/bower.json-spec#dependencies)

Anyway even if is not because of Bower, imo using tags is a good way to define stable versions

nathansmith commented 10 years ago

Just wanted to say I haven't forgotten this.

I recently switched jobs, and life was hectic up until that point.

I'll look into having a "semantic versioning" approach soon, hopefully.

nathansmith commented 9 years ago

Okay, Unsemantic is now tagged 1.0.1 (all I did was add a stand-alone reset.css file, since I needed it in a flat-CSS project). Yay. :)