{"action":"created","issue":{"url":"https://api.github.com/repos/HvyIndustries/crane/issues/91","repository_url":"https://api.github.com/repos/HvyIndustries/crane","labels_url":"https://api.github.com/repos/HvyIndustries/crane/issues/91/labels{/name}","comments_url":"https://api.github.com/repos/HvyIndustries/crane/issues/91/comments","events_url":"https://api.github.com/repos/HvyIndustries/crane/issues/91/events","html_url":"https://github.com/HvyIndustries/crane/issues/91","id":161378458,"number":91,"title":"Post-release notifications","user":{"login":"nevadascout","id":377089,"avatar_url":"https://avatars.githubusercontent.com/u/377089?v=3","gravatar_id":"","url":"https://api.github.com/users/nevadascout","html_url":"https://github.com/nevadascout","followers_url":"https://api.github.com/users/nevadascout/followers","following_url":"https://api.github.com/users/nevadascout/following{/other_user}","gists_url":"https://api.github.com/users/nevadascout/gists{/gist_id}","starred_url":"https://api.github.com/users/nevadascout/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nevadascout/subscriptions","organizations_url":"https://api.github.com/users/nevadascout/orgs","repos_url":"https://api.github.com/users/nevadascout/repos","events_url":"https://api.github.com/users/nevadascout/events{/privacy}","received_events_url":"https://api.github.com/users/nevadascout/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/HvyIndustries/crane/labels/feature","name":"feature","color":"128A0C"},{"url":"https://api.github.com/repos/HvyIndustries/crane/labels/proposed","name":"proposed","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-06-21T08:37:50Z","updated_at":"2016-06-21T14:18:16Z","closed_at":null,"body":"After a user has updated to the latest version of Crane or installed Crane for the first time, do we need to display a help message linking to the release notes and telling them how to get started?\r\n\r\nAlso, do we need to be able to force a rebuild of intellisense caches? If our release changes the way the treebuilder works (as 0.2 does), then we need to be able to invalidate a cache. Maybe we include the Crane version number in our hash calculation? eg. `projectname_version` is the string that gets hashed - then this will be done automatically when we increment the Crane version."},"comment":{"url":"https://api.github.com/repos/HvyIndustries/crane/issues/comments/227454045","html_url":"https://github.com/HvyIndustries/crane/issues/91#issuecomment-227454045","issue_url":"https://api.github.com/repos/HvyIndustries/crane/issues/91","id":227454045,"user":{"login":"TheColorRed","id":1571806,"avatar_url":"https://avatars.githubusercontent.com/u/1571806?v=3","gravatar_id":"","url":"https://api.github.com/users/TheColorRed","html_url":"https://github.com/TheColorRed","followers_url":"https://api.github.com/users/TheColorRed/followers","following_url":"https://api.github.com/users/TheColorRed/following{/other_user}","gists_url":"https://api.github.com/users/TheColorRed/gists{/gist_id}","starred_url":"https://api.github.com/users/TheColorRed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TheColorRed/subscriptions","organizations_url":"https://api.github.com/users/TheColorRed/orgs","repos_url":"https://api.github.com/users/TheColorRed/repos","events_url":"https://api.github.com/users/TheColorRed/events{/privacy}","received_events_url":"https://api.github.com/users/TheColorRed/received_events","type":"User","site_admin":false},"created_at":"2016-06-21T14:18:16Z","updated_at":"2016-06-21T14:18:16Z","body":"The cache currently does a `JSON.stringify(workspaceTree)` and then uses gzip to zip it up. What we could also do, is put in the Crane version that the cache was built with.\r\n\r\nFor example:\r\n\r\n```js\r\nvar workspaceTree = {\r\n    version: \"1.7.0\",\r\n    // Not sure if this is the best date format or not, but it is the same as a database timestamp\r\n    created: \"2016-06-18 14:24:55\", \r\n    updated: \"2016-06-21 10:11:12\",\r\n    tree: [\r\n        /* Object 1*/,\r\n        /* Object 2*/\r\n    ]\r\n}\r\n```\r\n\r\nI don't know if we want to link to changes or not, when the user searches for an to install or update, there is that **README** link on the right hand side of the extension. If your are thinking that the link will be different than the **Getting Started** or **Release Notes**, then maybe would be a good idea..."}}
{"actor":{"display_login":"TheColorRed"}}