Fixed bootstrap.php path in phpunit.xml.dist
Exclude vendor/ folder from default phpunit run

Once we start placing SS modules in vendor/,
we need to find a smarter solution...
Relaxed composer version requirements so that stable releases can be created.

Note that once sapphire, cms, and framework actually provide a stable version, '@stable' should put onto the end of the relevant require clauses.
Support for composer-created themes dir structure

Due to git limitations, we can't check out the blackcandy
"parent" theme into themes/blackcandy/ directly, since that
would require sharing paths with git repositories of other themes.
Added @stable markers to composer.json
Added composer.lock for 2.4.9
Removed composer.lock
Added phing support
Removed @stable tags from release branch

Same as 3.0.x-dev, they're only relevant for tags,
not for branches.
API Filter composer files in IIS and Apache rules (fixes #8011)

They can expose version information, so shouldn't be accessible
through the web. The better solution of course is to move
to a public/ subfolder application structure.
Merge remote-tracking branch 'origin/2.4' into 3.0

Conflicts:
	build.xml
	composer.json
	install.php
	phpunit.xml.dist
Prevent YAML access in IIS by default (fixes #8233)

Since SS3 keeps values in configuration, direct access
to known paths might expose them
API Block all yaml files by default, to reduce the change of information leakage
Forcing stable flags for release
Merge branch '3.0.5' into 3.0
Include a higher timeout value to avoid timeouts.

Checking out framework can often take longer than the default
(300 seconds). This gives a 10min limit to creating a new project.
Merge remote-tracking branch 'origin/3.0' into 3.1

Conflicts:
	composer.json