Fix Bug 1151579 - New Tabzilla v0.3.0 static package

[schalkneethling]

@alexgibson r?

[alexgibson]

We don't have much in the .gruntfile just yet, any reason not to start off be using Gulp?

[schalkneethling]

Is Gulp the new hotness ;) Used to using Grunt for all the things but, no reason we cannot use Gulp.

[alexgibson]

Is Gulp the new hotness ;) Used to using Grunt for all the things but, no reason we cannot use Gulp.

Entirely up to you on this one, they both work well for projects like this :+1:

[schalkneethling]

Hey, I like learning new things so, let me Gulp it up :runner:

[jpetto]

+1 for Gulp, and keeping lib.less as slim as possible.

[schalkneethling]

@jpetto both === done ;)

[alexgibson]

Should we add a default gulp task? (maybe just runs watch?)

[alexgibson]

Other than the points mentioned above, this looks good to me :+1:

[schalkneethling]

Yeah sure, let's do that re: default gulp task.

[schalkneethling]

@alexgibson Good to merge? The only potential problem here is the commit messages. I stupidly :blush: worked directly on master on my fork so, not sure how I can squash all these commits :cry:

[willkg]

You can do "git rebase -i " and pick a sha that's the point where you should have had your branch diverge at. That puts you in a mode where you can selectively squash, fixup, reword, etc the commits.

[schalkneethling]

Thanks @willkg however, I get this when I attempt a git rebase -i https://sneethling.pastebin.mozilla.org/8839482

[alexgibson]

If you have 11 commits, try git rebase -i HEAD~11?

[willkg]

Bah. fucking github comments. I wrote git rebase -i <sha> and it nixed the sha part.

[schalkneethling]

w00t!!! Thanks @willkg and @alexgibson now I have learned some new git foo \o/

[alexgibson]

LGTM, r+! :pineapple: