{"action":"created","issue":{"url":"https://api.github.com/repos/meteor/docs/issues/91","repository_url":"https://api.github.com/repos/meteor/docs","labels_url":"https://api.github.com/repos/meteor/docs/issues/91/labels{/name}","comments_url":"https://api.github.com/repos/meteor/docs/issues/91/comments","events_url":"https://api.github.com/repos/meteor/docs/issues/91/events","html_url":"https://github.com/meteor/docs/issues/91","id":181604535,"number":91,"title":"Include meteor/meteor/History.md in Docs","user":{"login":"abernix","id":841294,"avatar_url":"https://avatars.githubusercontent.com/u/841294?v=3","gravatar_id":"","url":"https://api.github.com/users/abernix","html_url":"https://github.com/abernix","followers_url":"https://api.github.com/users/abernix/followers","following_url":"https://api.github.com/users/abernix/following{/other_user}","gists_url":"https://api.github.com/users/abernix/gists{/gist_id}","starred_url":"https://api.github.com/users/abernix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abernix/subscriptions","organizations_url":"https://api.github.com/users/abernix/orgs","repos_url":"https://api.github.com/users/abernix/repos","events_url":"https://api.github.com/users/abernix/events{/privacy}","received_events_url":"https://api.github.com/users/abernix/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-10-07T07:46:47Z","updated_at":"2016-10-10T10:13:56Z","closed_at":"2016-10-10T00:52:15Z","body":"Currently, if you get a Meteor update to a new version, I'm not sure there is any clear path for you to see what has changed unless you're aware that GitHub is _the_ place to go.  There's [a History.md](https://github.com/meteor/meteor/blob/master/History.md) which is well maintained, but it's hard to find as GitHub might not be the first place many users go.  Aside from GitHub, Meteor.com would seem like the first logical place to head.\r\n\r\nBut even then, it appears the process would be something like this for many (most?) users:\r\n\r\n* Go to [Meteor.com](http://Meteor.com)\r\n* (optional, but likely, path) Click on **Install**\r\n * See no Release Notes\r\n * Try the Docs/Guide links there?\r\n* Click on **Developer** (at top)\r\n * Hmm, maybe Docs? or Guide?\r\n* Get to Docs/Guide\r\n * Guide: See Migration Guides, but nothing per version.  Click Docs (top right)\r\n * Docs: See nothing helpful.  Click Guide.\r\n * Maybe go to Forums?  But forums usually only has major releases.\r\n* Try to find the code source?\r\n * No link to the `meteor/meteor` GitHub\r\n * Google?\r\n\r\nIt would be best if Meteor.com had a <sub>tiny</sub> link to Release Notes under the \"Install\" button.  Or at least on the Install page.  Linking to the GitHub Repo might be abrupt UX (with no return path), so a nice option might be the Docs.  Unfortunately, Docs doesn't have Release Notes to link to right now.\r\n\r\nSince the `code` is already a submodule of `docs`, and `code` has a `History.md`, it seems like it might be possible to import this into Docs.\r\n\r\nSeed planted by: meteor/meteor#7881 & meteor/meteor#7870, both opened this week and semi-related to: meteor/meteor#6730."},"comment":{"url":"https://api.github.com/repos/meteor/docs/issues/comments/252579315","html_url":"https://github.com/meteor/docs/issues/91#issuecomment-252579315","issue_url":"https://api.github.com/repos/meteor/docs/issues/91","id":252579315,"user":{"login":"abernix","id":841294,"avatar_url":"https://avatars.githubusercontent.com/u/841294?v=3","gravatar_id":"","url":"https://api.github.com/users/abernix","html_url":"https://github.com/abernix","followers_url":"https://api.github.com/users/abernix/followers","following_url":"https://api.github.com/users/abernix/following{/other_user}","gists_url":"https://api.github.com/users/abernix/gists{/gist_id}","starred_url":"https://api.github.com/users/abernix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abernix/subscriptions","organizations_url":"https://api.github.com/users/abernix/orgs","repos_url":"https://api.github.com/users/abernix/repos","events_url":"https://api.github.com/users/abernix/events{/privacy}","received_events_url":"https://api.github.com/users/abernix/received_events","type":"User","site_admin":false},"created_at":"2016-10-10T10:13:56Z","updated_at":"2016-10-10T10:13:56Z","body":"@tmeasday This is great!  Agree to agree on the submodule updating – I'll certainly keep my own eyes on it.\r\n\r\n@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`](https://github.com/meteor/meteor/blob/devel/tools/cli/commands-packages.js#L2485) 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](http://docs.meteor.com/changelog.html) could be added [in this meteor code](https://github.com/meteor/meteor/blob/e86ef3cb47fb4f44a06b35433d94cae4602e7bcc/tools/runners/run-all.js#L364) 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."}}
{"actor":{"display_login":"abernix"}}