gistfile1.txt

https://github.com/electron/electron/pull/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](https://github.com/electron/electron/pull/7660) 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

- electron/electron-npm-packages
electron/i18n
electron/releases
electron/update-electron-app

- The `semantic-release` module is in use on eight projects in the @electron org so far: https://github.com/search?utf8=%E2%9C%93&q=%22npm+run+semantic-release%22+%40electron&type=Code

- https://github.com/electron/electron/pull/11937 `0.0.0-dev`