fix(select): fixed missing validation error when deselecting all values (select with required and multiple attributes)
fix(select): multi-select checkmark icon displays correctly without additional CSS

Reverts commit d167af80b5e055d8195559975216a1fde353230f and instead moves the checkmark icon element to before the label span. As the checkmark icon is "pull-right", it can be placed before the label.
fix(datepicker): correctly change view month when last day of month is selected

When the selected date corresponds to a day that doesn't exist in the next/previous month, the month change would not work correctly - either it would skip a month forward or it would not change to the previous month. This was caused by javascript date values rollover when changing month part of date because months have a different number of days.
This fix uses the first day of the month in the calculations to avoid the rollover.
fix(dropdown): clean up body click listeners upon destroy

Fixes JS exceptions and leaking event listeners as a result of 81235039438.

Clicking on the body calls hide(), which assumes $element is defined and tries to
remove an event handler. Calling destroy ultimately sets $element to null, which
causes subsequent calls to hide() to throw exceptions. Prior to this commit,
destroy() did not clean up event listeners on the body element, so the only way
those click handlers got removed was upon an actual click event which called
harmlessly through hide(). As a result of setting $element to null, however,
it could no longer harmlessly call through hide().

This resulted in both a lot of extra event listeners being registered on the
body element and never cleaned up, and also a lot of exceptions being thrown
any time a dropdown was removed by means of destroying its scope.
fix(tooltip): correctly bind/unbind events

Refactored events binding/unbinding code into separate methods to make it easier to identify events used.
Fixed unbinding of keyboard events when binded to 'element' instead of 'tipElement'.
Changed auto-close related event to not use anonymous handlers, so we can correctly unbind from the events.
docs(getting-started): add description for the two angular-strap files
fix(datepicker): add support to modelDateFormat for named date formats

The parsing of dates using named formats (shortDate, longDate, etc) was not working when used with modelDateFormat. Changed dateParser.parse to check and convert named formats to the corresponding token format before parsing date.

fix for #1249
docs(datepicker/timepicker): add modelDateFormat/modelTimeFormat description to docs
test(karma): setup SauceLabs testing
fix(select): multi-select checkmark icon displays correctly without additional CSS

Reverts commit d167af80b5e055d8195559975216a1fde353230f and instead moves the checkmark icon element to before the label span. As the checkmark icon is "pull-right", it can be placed before the label.
fix(tabs): add `track by $index` to the base template (fixes #1201)
test(tabs): add two simple test cases to check for `track by $index` on the tabs template
test(tabs): create a new set of tests for checking the functionality of nested tabs
fix($animate): update animate.enter() so new dom objects are inserted in the same place they were w/angular 1.2
this is due to changes from: https://github.com/angular/angular.js/commit/1cb8584e8490ecdb1b410a8846c4478c6c2c0e53

Conflicts:
	src/tooltip/tooltip.js
fix(typeahead): fix selected object display
chore(karma): switch ie remote testing to quieter platforms
chore(npm): update devDeps
chore(karma): tweak timeout configuration
test(datepicker): add test to check days order in datepicker

Added a new gulp task called 'test:timezone' that sets the environment timezone for PhantomJS to use. It expects a parameter on the command line with the name of the timezone to use, like: 'gulp test:timezone --America/Sao_Paulo'.
Using this new task, the new test that checks for days order in datepicker fails for America/Sao_Paulo because of changes in Daylight Saving Time - from what I could understand, Brazil changes the time at midnight and the datepicker uses dates with time set to midnight, so when it increments one day, it goes back to the previous day, which caused repeated days to show up on the calendar.
fix(datepicker): fix duplicate days in picker when DST changes

Depending on the browser timezone, the datepicker might show duplicate days when the DST causes hours to go back - this will happen in São Paulo, Brazil timezone in 18th October 2014 at midnight, when the time will go back 1 hour, so the datepicker will show two 18th days and miss the 19th, as shown in #1133.

If DST causes time to go forward, there is no problem because the day will still be incremented. If time goes back, the fix checks if hours are > 12, meaning we went back to original day, and add +2 hours to compensate for the hours going back, causing the day to increment as intended. (Code copied from jquery ui)