delta/gitlab/gitlab-ce.git, branch fix-capitalization

Fix capitalization in notification to be consistent with other notifications.

2016-10-25T18:41:01+00:00

Updated logo from @luke

2016-10-17T14:55:35+00:00

Merge branch 'fix-pipeline-metrics-failure' into 'master'

2016-10-17T13:41:03+00:00


Fix broken specs on MySQL

## What does this MR do?
Fixes broken master after https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6896

See merge request !6935

Merge branch 'fix_test_env' into 'master'

2016-10-17T13:08:40+00:00


Fix Test Env (proper error handling when gitlab-shell is not clonned)

## What does this MR do?

If we were not able to clone gitlab-shell we have to stop all test suite, for now we run it regardless we cloned it or not.

## Why was this MR needed?

To not confuse developers when build is red, to get fasts feedback, to save resources and time.

See merge request !6933

Merge branch 'safari-is-baNaNas' into 'master'

2016-10-17T12:51:09+00:00


Fix Safari displaying NaN for selected due date

## What does this MR do?

1. Stops using `Date.parse` to parse selected due dates. 
2. Refactors DueDateSelectors to be more maintainable and readable

## Are there points in the code the reviewer needs to double check?

**To review the actual fix, look here:** https://gitlab.com/gitlab-org/gitlab-ce/commit/4ad43ac3a12902d7ea01dc09f8a361b01c21a0ee. It would be difficult to pick out from the overall diff. 

## Why was this MR needed?

In Safari, the due date selector was displaying 'NaN' when a date is selected, which was being returned by `Date.parse`. Because `Date.parse` is implemented differently across browsers it's generally recommended to favor implicit Date parsing with the `Date` constructor. For more background on this, [see MDN on Date.parse](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Date/parse).

Also, the code for DueDateSelector was pretty messy, and its logic was very tightly coupled, so I refactored it. None of the basic logic changed, I just broke it up into smaller pieces and made it more OO. 

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/22984

See merge request !6797

Fix broken specs on MySQL after https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6896

2016-10-17T12:31:43+00:00

Fix Test Env (proper error handling when gitlab-shell is not clonned)

2016-10-17T11:41:29+00:00

Merge branch 'dz-fix-spinach-mr' into 'master'

2016-10-17T11:27:39+00:00


Fix randomly crashing spinach test for merge request

For https://gitlab.com/gitlab-org/gitlab-ce/issues/23378

See merge request !6932

Merge branch 'fix-spinach-atom-feed-failure-due-to-carriage-returns' into 'master'

2016-10-17T11:22:36+00:00


Fix atom feed spinach failure

## What does this MR do?

Replaces all carriage returns in the expected commit description.

Is a partial fix to...

> spinach 5 10 https://gitlab.com/gitlab-org/gitlab-ce/builds/5132637 - partial fix in !6910

As you can see, the other half of the fix to this build is in !6910.

## Are there points in the code the reviewer needs to double check?

## Why was this MR needed?

Failed spinach tests

## Screenshots (if relevant)

## Does this MR meet the acceptance criteria?

- [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
  - [ ] Added for this feature/bug
  - [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

## What are the relevant issue numbers?

See merge request !6922

Merge branch 'add-pipeline-metrics-worker' into 'master'

2016-10-17T11:03:51+00:00


Add Pipeline metrics worker

## What does this MR do?
Creating a new Merge Request metrics is time consuming, because we need to access repository.

This makes this operation asynchronous, thus non-blocking for updating pipeline.

## Are there points in the code the reviewer needs to double check?

## Why was this MR needed?

## Screenshots (if relevant)

## Does this MR meet the acceptance criteria?

- [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
  - [ ] Added for this feature/bug
  - [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

## What are the relevant issue numbers?

See merge request !6896