Include meteor/meteor/History.md in Docs about docs

[lorensr]

What about when a new version is downloaded and when someone updates, we print a link to the relevant section of History.md, or to the upgrade section of the Guide if there is one?

[laosb]

I'm thinking that we should have something automatically generate a rough list for History.md, and if we need to explain the entry further more, just add few words there. So we won't miss some changes or get confused since for now we're modifying entries on a per PR/commit pattern.

[tmeasday]

I added this: http://docs.meteor.com/changelog.html

Could probably be better (please improve y'all) but I think it helps anyway. I'll look into get a link on the homepage.

[tmeasday]

We'll probably want to be more militant in updating the submodule too so that doesn't get out of sync.

[abernix]

@tmeasday This is great! Agree to agree on the submodule updating – I'll certainly keep my own eyes on it.

@lorensr I think this (as in, a specific link to each new version) could be accomplished right now by amending and setting the banners (using the admin set-banners command) after each release. However, from what I gather, the need to link to a specific anchor/version in the change log would further complicate the already-complicated release process. Banners are currently only done on major versions, and in the future I think any time a banner is used, it's certainly reasonable to include the direct link. As a stopgap measure for smaller releases, perhaps just a link to this new change log could be added in this meteor code which is outputted when the an update is complete? I believe that's the only point where it would need to be displayed. That would be best for a PR over at meteor though.