Fixing FormField not setting readonly attribute on setReadonly(true)
Fix: WYSIWYG now returns valid HTML in tables

The WYSIWYG by default creates invalid HTML5. Creating a table and running it through W3C validator returns the following error: The border attribute on the table element is obsolete. Use CSS instead.
Update dataobject.md

This page is grid-field not gridfield.
Merge pull request #3009 from scottmcmurray/patch-1

Update dataobject.md
Info about getting set up using composer and MAMP

Added by request of Gábor Novoszádi from community feedback and thanks to the gist from @kkirsche. I have supplied a link to the gist as it is well written, with permission we may look to rework for direct inclusion at some point :)
Docs / Tests for Director::absoluteURL
Merge pull request #3011 from tractorcow/pulls/absurl

Docs / Tests for Director::absoluteURL
Prevent IE errors on hidden login forms

In order to focus a field, it needs to be visible,
which can't be guaranteed on a core level by the login form JavaScript.
Optionally check for visibility via jQuery if it exists,
and allow explicit disabling of this behaviour via a unique identifier.
Add 3.0.10 upgrade docs
Merge pull request #3010 from camfindlay/patch-3

Info about getting set up using composer and MAMP
FIX - missing link url for composer

My bad, have amended this.
Merge pull request #3014 from camfindlay/patch-4

FIX - missing link url for composer
Delete formatted images after image upload

This change fixes an issue where old/existing formatted images are used
when a filename is reused (by overwrite or by coincidence), regardless
of if the file contents have changed. To users this mainly manifests
as a file overwrite appearing not to work; the thumbnails in the CMS
show the original image until regeneration is forced.

Calling Image::deleteFormattedImages() after image upload ensures that
no stagnant formatted images will be used.
Merge remote-tracking branch 'composer/3.0.10' into 3.1.4
3.1.4 upgrading docs
BUG Fix Date and SS_DateTime::FormatFromSettings
This issue is caused by the odd default behaviour of Zend_Date, which attempts to parse yyyy-mm-dd format date and times as though they were yyyy-dd-mm.
Update upgrading docs 3.1.4
Merge remote-tracking branch 'origin/3.0' into 3.1
Merge remote-tracking branch 'origin/3.1.4' into 3.1
Merge pull request #3013 from silverstripe-iterators/pulls/login-form-js

Prevent IE errors on hidden login forms