Ignore build-related files in "git archive" (fixes #8167)

This is useful for keeping standard "composer create-project"
checkouts clean. Unless they use "--keep-vcs", in which case
.gitattributes is (correctly) ignored.

This has the side effect that archive-checkouts can't
run phing or phpunit scripts, but I think that's
acceptable.
IIS 7.5 does not like forward slash at the end of silverstripe-cache

IIS 7.5 does not like forward slash at the end of silverstripe-cache
Merge pull request #32 from sunnysideup/patch-1

IIS 7.5 does not like forward slash at the end of silverstripe-cache
Merge pull request #29 from chillu/pulls/gitattributes

Ignore build-related files in "git archive" (fixes #8167)
Remove require-dev section, composer doesn't handle it well

Any "composer require <module>" call will first call
a "composer update". This *automatically* includes dev requirements,
without providing a way to turn off this behaviour.
A workaround would be "composer require --no-update <module> && composer update --no-dev <module>",
but that drastically reduces the usefulness of the command
for our target audience (moderately technical devs).

In the end, the small faction of devs needing the dev dependencies
also know how to install them on their own. And having a local phpunit
build actually gets in the way more than it helps in case you have
it installed through PEAR already (can get really weird when using the
PEAR provided "phpunit" binary, but the autoloader finds the composer managed classes).
Merge pull request #36 from chillu/pulls/require-dev

Remove require-dev section, composer doesn't handle it well
Updated behat.yml to reflect changes in behat-extension module
Merge remote-tracking branch 'origin/3.0' into 3.1
FIX: Put self.version in composer dependencies.

Now that https://github.com/composer/composer/pull/1883 is in Composer, self.version
will work as a requirement for framework & cms.  This will simplify the release
process a great deal.

Ultimately, the release of rc1 will be the place to test that, but it seems appropriate
to get this in there for that.

If it succeeds with 3.1-rc1, I'd suggest we backport to 3.0 and 2.4.
Merge pull request #39 from sminnee/composer-uses-self-version

FIX: Put self.version in composer dependencies.
Updated github path
Updated github path
case insensitive the assets/ allowed extensions for Apache
Merge pull request #40 from NightJar/hackfest_may_2013

case insensitive the assets/ allowed extensions for Apache
HTML5 video file types.
Merge pull request #41 from uniun/HTML5-video-file-types

HTML5 video file types.
NEW: Added post-install and post-update dev/build call.

With this change, composer will automatically call dev/build after an update or install
command.  The main reason that this is 3.1-only is that previous releases would have
necessitated the use of 'sudo -u www-data', which is too environment-specific.

One thing that this may cause problems with is 'composer create-project' in an environment
without a _ss_environment file.  It will call dev/build, and dev/build will throw an
error.  That should be fixed in a subsequent commit.
git commit -m "FIX: Move install composer.json to use self.version.

Now that Composer has been fixed, self.version can be used as a dependency for framework
and cms in installer.  This simplifies our composer.json, and meanst that we can commit
composer.lock into the repo, as required.  An annoying piece of our release process has
been solved!
Merge branch '3.0' into 3.1
Merge pull request #42 from sminnee/composer-post-install

NEW: Added post-install and post-update dev/build call.