search

Compass / compass-blueprint

blueprint compass extension
http://compass-blueprint.org/
MIT License
17 stars 8 forks source link

Please make a formal release #2

Closed jonassmedegaard closed 10 years ago

jonassmedegaard commented 10 years ago

Recent formal releases of Compass ships without Blueprint.

Please issue formal release of this Blueprint-as-separate-theme project, to avoid regressions for users of older Compass who relied on Blueprint.

stephenway commented 10 years ago

Hey @jonassmedegaard, it's released on RubyGems as compass-blueprint, we even have a new site for the project compass-blueprint.org.

jonassmedegaard commented 10 years ago

Quoting Stephen Way (2014-08-25 19:15:11)

Hey [1]@jonassmedegaard, it's released on RubyGems as compass-blueprint, we even have a new site for the project compass-blueprint.org.

Yes, I am aware of both RubyGems and website.

What I suggest is to tag here on github what corresponds with RubyGems releases.

chriseppstein commented 10 years ago

@jonassmedegaard I don't understand what you mean by "What I suggest is to tag here on github what corresponds with RubyGems releases."

jonassmedegaard commented 10 years ago

I am a Debian developer. I redistribute Compass and Compass::Blueprint as Debian packages - i.e. not as gem packages.

For maintenance of the Debian packages, I prefer to track both what you guys decide is "final" and the git commits leading to that stage - as that eases triangulating issues that may arise, and also sometimes helps understand how you ended at design choices that are maybe weakly documented.

Hope that clarifies my interest in you tagging releases here.

chriseppstein commented 10 years ago

blueprint is not part of compass. It is a compass extension now. So it is versioned independently of compass now. It has it's own version dependencies on compass.

jonassmedegaard commented 10 years ago

Quoting Chris Eppstein (2014-08-26 22:48:25)

blueprint is not part of compass. It is a compass extension now. So it is versioned independently of compass now. It has it's own version dependencies on compass.

Yes. I am aware of that.

...but fail to understand how that is relevant to my request that you tag releases here at github.

scottdavis commented 10 years ago

I dont think its too much to ask that compass-blueprint gets git tags for its releases. We do this in compass automaticly with a rake task surely we can get this working here.

chriseppstein commented 10 years ago

Sorry, I thought this was an issue filed against compass proper. So many issue emails in my inbox >_<

scottdavis commented 10 years ago

Im fixing it now

scottdavis commented 10 years ago

SInce we never had set it up i updated the gemspec and bumped the versioning to start at 1.0.0 it was never tagged as you said and since compass 1.0.0 is the first official decoupling of blueprint i think it was only fair to start compass-blueprint out at 1.0.0 also.

TL;DR; I've pushed the 1.0.0 to rubygems and set a tag in git.

stephenway commented 10 years ago

Thanks guys!

jonassmedegaard commented 10 years ago

Quoting Scott Davis (2014-08-27 00:42:33)

Im fixing it now

Excellent. Thanks!