search

flazz / vim-colorschemes

one colorscheme pack to rule them all!
3.44k stars 630 forks source link

Please define releases for vim-colorschemes #50

Closed tim-lebedkov closed 6 years ago

tim-lebedkov commented 10 years ago

It would be nice if you could define releases. It is unclear what is stable and what is not.

zachgersh commented 10 years ago

Do you want some sort of tagged release? Seems like you should be able to pull the colorschemes at any time and have them be stable!

tim-lebedkov commented 10 years ago

well, actually I want to create releases for this package https://npackd.appspot.com/p/vim-colorschemes It also makes it clearer whether something big has changed (e.g. 1.3->2.0) etc.

I must admit that color schemes in Vim are probably not the most complicated code so I'll be OK with any decision.

flazz commented 9 years ago

I agree with @zachgersh each git revision is a release :), There is no abi or api compatibilities that a version helps solve … just a bunch of themes.

But to your immediate issue, I can think of a few options:

what if you versioned your packages on time based snapshots: 15.8 -> October 15, 2015, etc. kinda like how ubuntu does it? possibly with an extension like 15.8-gf1ade59eff where the g ties it to the commit?

Alternatively you could count the number of commits from the first one and use that? This might be more aligned with "when big things change".