2018-01-05: lbennett stable merge

What does this MR do?

• @filipa - app/assets/javascripts/projects/project_new.js
• @dzaporozhets - app/assets/javascripts/vue_merge_request_widget/mr_widget_options.js
• @mayra-cabrera - app/models/concerns/deployment_platform.rb
• @felipefac - doc/api/boards.md
• @Ninir - doc/api/settings.md
• @felipefac - lib/api/entities.rb
• @jprovaznik - spec/fixtures/api/schemas/entities/merge_request_widget.json
• @filipa - spec/javascripts/lib/utils/text_utility_spec.js

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 entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Review
  • Has been reviewed by UX
  • Has been reviewed by Frontend
  • Has been reviewed by Backend
  • Has been reviewed by Database
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• Internationalization required/considered
• If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan

What are the relevant issue numbers?

Closes #10 (closed)