{"action":"closed","issue":{"url":"https://api.github.com/repos/CredentialTransparencyInitiative/vocabularies/issues/143","repository_url":"https://api.github.com/repos/CredentialTransparencyInitiative/vocabularies","labels_url":"https://api.github.com/repos/CredentialTransparencyInitiative/vocabularies/issues/143/labels{/name}","comments_url":"https://api.github.com/repos/CredentialTransparencyInitiative/vocabularies/issues/143/comments","events_url":"https://api.github.com/repos/CredentialTransparencyInitiative/vocabularies/issues/143/events","html_url":"https://github.com/CredentialTransparencyInitiative/vocabularies/issues/143","id":184650802,"number":143,"title":"CTDL \"release\" process and timetable","user":{"login":"stuartasutton","id":2939046,"avatar_url":"https://avatars.githubusercontent.com/u/2939046?v=3","gravatar_id":"","url":"https://api.github.com/users/stuartasutton","html_url":"https://github.com/stuartasutton","followers_url":"https://api.github.com/users/stuartasutton/followers","following_url":"https://api.github.com/users/stuartasutton/following{/other_user}","gists_url":"https://api.github.com/users/stuartasutton/gists{/gist_id}","starred_url":"https://api.github.com/users/stuartasutton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stuartasutton/subscriptions","organizations_url":"https://api.github.com/users/stuartasutton/orgs","repos_url":"https://api.github.com/users/stuartasutton/repos","events_url":"https://api.github.com/users/stuartasutton/events{/privacy}","received_events_url":"https://api.github.com/users/stuartasutton/received_events","type":"User","site_admin":false},"labels":[{"id":477681597,"url":"https://api.github.com/repos/CredentialTransparencyInitiative/vocabularies/labels/Documentation","name":"Documentation","color":"e99695","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/CredentialTransparencyInitiative/vocabularies/milestones/1","html_url":"https://github.com/CredentialTransparencyInitiative/vocabularies/milestones/Release%20-%202016-11-17%20","labels_url":"https://api.github.com/repos/CredentialTransparencyInitiative/vocabularies/milestones/1/labels","id":2119296,"number":1,"title":"Release - 2016-11-17 ","description":"This is the first CTDL release.","creator":{"login":"jkitchensSIUC","id":20917206,"avatar_url":"https://avatars.githubusercontent.com/u/20917206?v=3","gravatar_id":"","url":"https://api.github.com/users/jkitchensSIUC","html_url":"https://github.com/jkitchensSIUC","followers_url":"https://api.github.com/users/jkitchensSIUC/followers","following_url":"https://api.github.com/users/jkitchensSIUC/following{/other_user}","gists_url":"https://api.github.com/users/jkitchensSIUC/gists{/gist_id}","starred_url":"https://api.github.com/users/jkitchensSIUC/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jkitchensSIUC/subscriptions","organizations_url":"https://api.github.com/users/jkitchensSIUC/orgs","repos_url":"https://api.github.com/users/jkitchensSIUC/repos","events_url":"https://api.github.com/users/jkitchensSIUC/events{/privacy}","received_events_url":"https://api.github.com/users/jkitchensSIUC/received_events","type":"User","site_admin":false},"open_issues":19,"closed_issues":5,"state":"open","created_at":"2016-11-07T15:39:07Z","updated_at":"2016-11-15T19:25:52Z","due_on":"2016-11-16T00:00:00Z","closed_at":null},"comments":4,"created_at":"2016-10-22T19:57:38Z","updated_at":"2016-11-15T19:25:52Z","closed_at":"2016-11-15T19:25:52Z","body":"@jkitchensSIUC, several weeks ago, Nate, Mike and I discussed on our call a \"release\" process and getting a needed \"release\" out the door. We define a \"release\" as a (permanently) frozen (to everyone!) snapshot of the associated spreadsheets (properties, classes, controlled vocabularies, and json context). We should most likely date-stamp the names of the associated spreadsheets for a release and identify the release accordingly. The general process would be replicate the frozen, date-stamped spreadsheets as a \"pending\", publicly available, dynamic development version. When work on the pending version is deemed complete, it is frozen with date-stamped name, and the cycle repeats. With each snapshot, the github schema versions (including the json context) are updated from the frozen spreadsheets. There should be a \"Pending History\" page that is updated as new things are added and changes made in the pending state of the spreadsheets etc. (see, for example [1]).\n\nEach snapshot \"release\" must be documented on a permanent \"Release History\" page (see, for example [2]) with: (1) itemization (not explanation) of what has changed; and (2) itemization of anything that remains \"unstable\" (i.e., risky to use). Each \"release\" must be announced through **some broadcast mechanism** that pushes update messages to subscribers who have individually joined the channel. This communication channel should be used for **no other purpose** beyond announcing changes to the CTDL (including links to github issues discussing those changes and actions taken).\n\nWe need to get a 0.9? snapshot out the door as quickly as possible (i.e., now?) and declare a soft, approximated update cycle during the ongoing period of initial development--perhaps every 2-3 months? If we include statements of what is unstable in our release history, by implication, everything else is deemed stable and needs to follow the principle of \"change nothing that breaks systems\" (and that means other people's systems, not just ours).  \n\nCan we target a release within the next 1-2 weeks? That's possible only is we are confident that we've covered the 'significant' changes in what we already have.\n\nStuart\n\n[1] http://pending.schema.org/\n[2] http://schema.org/docs/releases.html\n"}}
{"actor":{"display_login":"jkitchensSIUC"}}