search

at-import / SassyLists

MIT License
276 stars 27 forks source link

Roadmap 2.0 #33

Closed KittyGiraudel closed 10 years ago

KittyGiraudel commented 10 years ago
lolmaus commented 10 years ago

Unit tests! I hope i don't need to explain how important they are and how they stabilize the quality of the code.

Sass unit testing isn't full-featured, but just enough to test a library like this. There are a number of libraries to choose from: true, sassquatch and a custom approach. I haven't used any... yet.

KittyGiraudel commented 10 years ago

I am already running tests for SassyLists, using Bootcamp: https://github.com/Team-Sass/SassyLists/tree/master/test. Every function is heavily tested.

lolmaus commented 10 years ago

Oh, it's just that the next branch lacks tests then.

KittyGiraudel commented 10 years ago

The next branch is obsolete. I have to remove it.

lolmaus commented 10 years ago

D'oh! Do you want me to reapply my PR to master?

KittyGiraudel commented 10 years ago

Don't bother, I'll add it manually. :)

lolmaus commented 10 years ago

Okay.

This confusion is an argument for renaming branches so that they correspond to version numbers, e.g. 1.x, 2.x.

KittyGiraudel commented 10 years ago

Next branch will be called 2.0.0. :)

lolmaus commented 10 years ago

2.0.0 isn't a good choice either. Specific versions are for tags. A branch name should correspond to a group of tags.

I did a little googling and found an article expanding on this issue: http://rentzsch.tumblr.com/post/45552867242/semantic-version-branches-for-submodules

KittyGiraudel commented 10 years ago

Released.

lolmaus commented 10 years ago

Congrats!