{"action":"created","issue":{"url":"https://api.github.com/repos/mastercoin-MSC/mastercore/issues/292","labels_url":"https://api.github.com/repos/mastercoin-MSC/mastercore/issues/292/labels{/name}","comments_url":"https://api.github.com/repos/mastercoin-MSC/mastercore/issues/292/comments","events_url":"https://api.github.com/repos/mastercoin-MSC/mastercore/issues/292/events","html_url":"https://github.com/mastercoin-MSC/mastercore/issues/292","id":59516103,"number":292,"title":"Release: binaries and release process","user":{"login":"dexX7","id":5836089,"avatar_url":"https://avatars.githubusercontent.com/u/5836089?v=3","gravatar_id":"","url":"https://api.github.com/users/dexX7","html_url":"https://github.com/dexX7","followers_url":"https://api.github.com/users/dexX7/followers","following_url":"https://api.github.com/users/dexX7/following{/other_user}","gists_url":"https://api.github.com/users/dexX7/gists{/gist_id}","starred_url":"https://api.github.com/users/dexX7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dexX7/subscriptions","organizations_url":"https://api.github.com/users/dexX7/orgs","repos_url":"https://api.github.com/users/dexX7/repos","events_url":"https://api.github.com/users/dexX7/events{/privacy}","received_events_url":"https://api.github.com/users/dexX7/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":52,"created_at":"2015-03-02T17:49:27Z","updated_at":"2015-03-07T06:54:18Z","closed_at":null,"body":"Ideally binaries would be created deterministically via Gitian, which is feasible to some degree.\r\n\r\nDue to the rebranding from Bitcoin Core to Master/Omni Core, some adjustments need to be made though.\r\n\r\nI basically see three options in general:\r\n\r\n- fully rebrand the whole project, use Gitian\r\n- temporarily revert the rebrand, create binaries via Gitian and rename the files manually\r\n- just build the binaries somehow and distribute them as done with earlier releases\r\n\r\nOption 1 would be anything but trivial (#289), and I really don't like option 3 for a lot of reasons, so I'm going to focus on 2, and how the release could be handled:\r\n\r\n1. Finalize 0.0.9.1\r\n2. Merge into upstream ([mastercoin-MSC/mastercore](https://github.com/mastercoin-MSC/mastercore) or [OmniLayer/omnicore](https://github.com/OmniLayer/omnicore)?)\r\n3. Tag the release\r\n4. Setup build environment in a VM (see: [slightly outdated tutorial, which I could update](https://gist.github.com/dexX7/b46f0fea46b9ea881142))\r\n5. Locally revert the file name changes (see: [419045f8a022b9dfd482cd3245331fbe34aa6a24](https://github.com/dexX7/bitcoin/commit/419045f8a022b9dfd482cd3245331fbe34aa6a24))\r\n6. Create binaries for Unix, Windows, and ideally Mac\r\n7. Rename binaries back to mastercored, mastercore-qt, ...\r\n8. Check that at least two parties come up with identical results\r\n9. Create file checksums and ideally GPG sign the files\r\n10. Publish binaries, checksums and signatures\r\n11. Announce release (blog, forums, mailing lists, ...)\r\n\r\nI'd prefer a release [based on Bitcoin Core 0.9.4](https://github.com/zathras-crypto/mastercore/compare/0.0.9.1-Z...bitcoin:0.9), especially because 0.9.3 misses the BIP 66 switch over logic etc. for the upcoming soft-fork, but this seems to be out of the scope of this issue.\r\n\r\nGoing this route would provide at least deterministically build binaries for Unix and Windows, and given that the UI release seems to target the end user base instead of integrators, stepping up here seems reasonable and justified to me.\r\n\r\n---\r\n\r\n@CraigSellars: I agree that option 2 is the most expedient/reasonable (and let’s use mastercoin-MSC/mastercore for this).\r\n\r\n--- \r\n\r\n@zathras-crypto: Not sure where my notes ended up here - perhaps wrong thread or a missed click on comment :(\r\n\r\nTL:DR; option 2 sounds most viable for me also. Had a few other comments, most not terribly important but one thing I was interested in is trust related to GPG keys - eg I have a GPG key I setup with Faiz a while ago, but how does Joe Q end user know it's my key?"},"comment":{"url":"https://api.github.com/repos/mastercoin-MSC/mastercore/issues/comments/77676930","html_url":"https://github.com/mastercoin-MSC/mastercore/issues/292#issuecomment-77676930","issue_url":"https://api.github.com/repos/mastercoin-MSC/mastercore/issues/292","id":77676930,"user":{"login":"dexX7","id":5836089,"avatar_url":"https://avatars.githubusercontent.com/u/5836089?v=3","gravatar_id":"","url":"https://api.github.com/users/dexX7","html_url":"https://github.com/dexX7","followers_url":"https://api.github.com/users/dexX7/followers","following_url":"https://api.github.com/users/dexX7/following{/other_user}","gists_url":"https://api.github.com/users/dexX7/gists{/gist_id}","starred_url":"https://api.github.com/users/dexX7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dexX7/subscriptions","organizations_url":"https://api.github.com/users/dexX7/orgs","repos_url":"https://api.github.com/users/dexX7/repos","events_url":"https://api.github.com/users/dexX7/events{/privacy}","received_events_url":"https://api.github.com/users/dexX7/received_events","type":"User","site_admin":false},"created_at":"2015-03-07T06:54:18Z","updated_at":"2015-03-07T06:54:18Z","body":"Yup, sure. :)"}}