{"action":"created","issue":{"url":"https://api.github.com/repos/golang/go/issues/18136","repository_url":"https://api.github.com/repos/golang/go","labels_url":"https://api.github.com/repos/golang/go/issues/18136/labels{/name}","comments_url":"https://api.github.com/repos/golang/go/issues/18136/comments","events_url":"https://api.github.com/repos/golang/go/issues/18136/events","html_url":"https://github.com/golang/go/issues/18136","id":192844762,"number":18136,"title":"proposal: make it trivial to obtain and test code against new go releases","user":{"login":"fgergo","id":5156576,"avatar_url":"https://avatars.githubusercontent.com/u/5156576?v=3","gravatar_id":"","url":"https://api.github.com/users/fgergo","html_url":"https://github.com/fgergo","followers_url":"https://api.github.com/users/fgergo/followers","following_url":"https://api.github.com/users/fgergo/following{/other_user}","gists_url":"https://api.github.com/users/fgergo/gists{/gist_id}","starred_url":"https://api.github.com/users/fgergo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgergo/subscriptions","organizations_url":"https://api.github.com/users/fgergo/orgs","repos_url":"https://api.github.com/users/fgergo/repos","events_url":"https://api.github.com/users/fgergo/events{/privacy}","received_events_url":"https://api.github.com/users/fgergo/received_events","type":"User","site_admin":false},"labels":[{"id":236419512,"url":"https://api.github.com/repos/golang/go/labels/Proposal","name":"Proposal","color":"ededed","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/golang/go/milestones/30","html_url":"https://github.com/golang/go/milestones/Proposal","labels_url":"https://api.github.com/repos/golang/go/milestones/30/labels","id":1373555,"number":30,"title":"Proposal","description":"Proposals that are pending (not yet accepted/rejected).\r\n","creator":{"login":"rsc","id":104030,"avatar_url":"https://avatars.githubusercontent.com/u/104030?v=3","gravatar_id":"","url":"https://api.github.com/users/rsc","html_url":"https://github.com/rsc","followers_url":"https://api.github.com/users/rsc/followers","following_url":"https://api.github.com/users/rsc/following{/other_user}","gists_url":"https://api.github.com/users/rsc/gists{/gist_id}","starred_url":"https://api.github.com/users/rsc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rsc/subscriptions","organizations_url":"https://api.github.com/users/rsc/orgs","repos_url":"https://api.github.com/users/rsc/repos","events_url":"https://api.github.com/users/rsc/events{/privacy}","received_events_url":"https://api.github.com/users/rsc/received_events","type":"User","site_admin":false},"open_issues":40,"closed_issues":91,"state":"open","created_at":"2015-10-24T01:40:49Z","updated_at":"2016-12-07T06:38:59Z","due_on":null,"closed_at":null},"comments":16,"created_at":"2016-12-01T13:20:00Z","updated_at":"2016-12-07T09:24:31Z","closed_at":null,"body":"(was: direct email to adg titled \"proposal on getting more people to test beta, -rc releases\". Adg suggested to continue on golang-dev, but since this is a proposal, golang-dev shall receive a notification with an issue id on the concrete proposal according to https://github.com/golang/proposal.)\r\n\r\nThough the goal is the same (to get better test coverage for beta and rc releases), this is a proposal about a process change, not about the complex tool and process change I sent as an rfc to golang-dev https://groups.google.com/forum/#!topic/golang-dev/kycbtvTIBAA\r\n\r\n(Original direct email revised for clarity.)\r\n\r\n### Proposal\r\nto include immediate value proposition (or expectation or hope...) in beta and rc announcements:\r\n1. if somebody planned to work on something earlier, a  personal one-line reply on it (e.g. if it was useful or ready or not useful or whatever)\r\n2. and/or no more than 1 or 2 personal new favourites from 2-3 tip users in the announcement email (e.g. \"1.8 has new go bug, contrary to it's name it helps me. signed me.\")\r\n\r\n### Assumption\r\n(This may be a bit off, but I think the big picture for possible non golang-dev beta or -rc testers is something like this.)\r\nIn the morning:\r\n1. \"hmm, a new go beta. Ok almost all previous final go releases were good or more like exceptionally useful for me.\"\r\n2. \"my current go release is working fine.\"    <--- that's probably high value for a possible non golang-dev beta tester\r\n3. \"simple upgrade to a final is easy. Testing a beta sounds like work I didn't plan and I am not used to it. Let's see, I need to at least: download, install, configure, select what to test, select how to test, then test-test, test, then possibly report in some useful way if something is not like I expect it to be, possibly with a minimal repro. Uhh, that's a lot and doing only some subset of these is not even useful in general.\"\r\n4. \"ok, what do I get, hmmm I should probably check the draft release notes in the announcement.\"\r\n5. ok, let's see... beta.golang.org/doc/go1.8 If I understand correctly, I'll need to read and evaluate all of these to decide if I get any immediate value in testing the beta.\r\n6. \"although I get everything for free and I could give back now by testing the beta. Maybe later. I'll test this later, when it's probably more immediately valuable for me.\"\r\n\r\n### To confirm,\r\nnice change in value proposition since the last beta announcement:\r\n\"There are no known problems or regressions.\"   <--- that's a high value statement. Although this possibly high value is immediately lowered after clicking and seeing \"Known Issues\".\r\n"},"comment":{"url":"https://api.github.com/repos/golang/go/issues/comments/265397432","html_url":"https://github.com/golang/go/issues/18136#issuecomment-265397432","issue_url":"https://api.github.com/repos/golang/go/issues/18136","id":265397432,"user":{"login":"fgergo","id":5156576,"avatar_url":"https://avatars.githubusercontent.com/u/5156576?v=3","gravatar_id":"","url":"https://api.github.com/users/fgergo","html_url":"https://github.com/fgergo","followers_url":"https://api.github.com/users/fgergo/followers","following_url":"https://api.github.com/users/fgergo/following{/other_user}","gists_url":"https://api.github.com/users/fgergo/gists{/gist_id}","starred_url":"https://api.github.com/users/fgergo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgergo/subscriptions","organizations_url":"https://api.github.com/users/fgergo/orgs","repos_url":"https://api.github.com/users/fgergo/repos","events_url":"https://api.github.com/users/fgergo/events{/privacy}","received_events_url":"https://api.github.com/users/fgergo/received_events","type":"User","site_admin":false},"created_at":"2016-12-07T09:24:31Z","updated_at":"2016-12-07T09:24:31Z","body":"@josharian sorry about my (deleted) comment about windows' exit command.\r\nNow I believe I understand better what's happening:\r\nmake.bat has an error, last 5 lines from make.bat (both 1.4 and 1.8beta1):\r\n:fail\r\nset GOBUILDFAIL=1\r\nif x%GOBUILDEXIT%==x1 exit %GOBUILDFAIL%\r\n\r\n:end\r\n\r\nSince GOBUILDEXIT is never set, make.bat finishes without error --> goversion assumes go1.4 is ready. (sidenote: all.bat checks for GOBUILDFAIL, that's why I think nobody noticed until now.)\r\n\r\n@brad I am not sure how to progress here, change 1.4 make.bat, change tip make.bat?\r\n\r\nIf I understand the situation correctly: still goversion needs some other mechanism to check for failed make.bat. Will respond on josharian/goversion#1 when I have some sensible hack/workaround. (Maybe run make.bat from a shell script and check for GOBUILDFAIL.)\r\n"}}
{"actor":{"display_login":"fgergo"}}