Add `rss` to the list of reserved post titles/slugs.

closes #1880
- added `rss` to core/server/models `generateSlug` reserved keywords
- added integration test for safe slug generation to core/test/integration/model/model_posts_spec.js
Fix hanging loading bar on deleting a post

Closes #1869

- Added an additional event listener for destroy event, then a listener
on the model for the sync event to finish the progress bar loader
Merge pull request #1885 from nicovalencia/issue-1880

Add `rss` to the list of reserved post titles/slugs.
Merge pull request #1886 from jgable/progressBarOnDelete

Fix hanging loading bar on deleting a post
Add bug report template link to CONTRIBUTING.md

There is now a GitHub link you can use to create a bug with the template.
Merge pull request #1888 from hswolff/additional-ux

Update placeholder of published data in editor
Shims for deleted (refactored away) files

closes #1873.
During file system merge upgrades of new releases, old files are not removed and node's require loads the old file instead of all the new ones in the new directory. The files in this commit act as a delegate for all other dependent scripts. These shim files explicitly require the new index.js.
Merge pull request #1883 from mattflo/master

Restored files that were refactored away.
Notifications can be dismissed with ESC

issue #1558

- this is a partial / short term fix for the problem with extra long notifications, so that there is at least one way to remove them.
Merge pull request #1894 from ErisDS/issue-1558

Notifications can be dismissed with ESC
Bump version for pre-release 2
Updating to latest Casper
Removing changelog from release

- this isn't required on account of GitHub & it being ENORMOUS
Change help text wording on settings page
Improve bootstrap flow of a Ghost application

addresses #1789, #1364

- Moves ./core/server/loader -> ./core/bootstrap.
The bootstrap file is only accessed once during startup,
and it’s sole job is to ensure a config.js file exists
(creating one if it doesn’t) and then validates
the contents of the config file.

Since this is directly related to the initializing 
the application is is appropriate to have 
it in the ./core folder, named bootstrap as that
is what it does.

This also improves the dependency graph, as now
the bootstrap file require’s the ./core/server/config
module and is responsible for passing in the validated
config file.

Whereas before we had ./core/server/config
require’ing ./core/server/loader and running its
init code and then passing that value back to itself,
the flow is now more straight forward of
./core/bootstrap handling initialization and then
instatiation of config module

- Merges ./core/server/config/paths into 
./core/server/config
This flow was always confusing me to that some config
options were on the config object, and some were on
the paths object.

This change now incorporates all of the variables
previously defined in config/paths directly
into the config module, and in extension,
the config.js file.

This means that you now have the option of deciding
at startup where the content directory for ghost
should reside.

- broke out loader tests in config_spec to bootstrap_spec

- updated all relevant files to now use config().paths

- moved urlFor and urlForPost function into 
 ./server/config/url.js