Skip to content

Instantly share code, notes, and snippets.

@zeke
Created June 20, 2018 18:36
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save zeke/a334a8623de6fb0de4147ede8297e7c9 to your computer and use it in GitHub Desktop.
Save zeke/a334a8623de6fb0de4147ede8297e7c9 to your computer and use it in GitHub Desktop.

electron/electron#13042

Updated CI configs for nightly release builds

https://twitter.com/bitandbang/status/996813228196941824

Tribal knowledge sucks for everyone.

It's burdensome for owners of it because they need to spend a TON of time transferring it. It's burdensome for seekers of it because they need to spend a TON of time seeking and deciphering it.

Destroy tribal knowledge by writing it down.

Throughout the life of this project, from atom-shell to electron-prebuilt to electron, there has been a de facto person responsible for releases. This was not by design. It just... happened.

For the first four years, @zcbenz was the only human on Earth who knew how to release Electron. Then we wrote down the release steps in late 2016, and yours truly became the second person to cut a release. Then the torch was silently passed to @kevinsawicki, who carried it dutifully for a time. When Kevin moved to another team at GitHub, @jkleinsc stepped up and took it over. More recently @ckerr has picked up the craft.

The process has improved over the years, and the process is now in the heads for more individuals. But we can do more! Let's get to a place where releases happen without the need for a specific individual. I think this will reduce stress on individuals and make for smoother and more transparent process that the whole contributor community can see and understand.

Semantic Versioning

Semantic Release

https://github.com/probot/semantic-pull-requests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment