Completing Releases and Nightly Builds

2nd chunk of `docs/src/development/releases.md`

9bc2337086f6ff9eb94dfe4fab67171fce66aa3fffc5504c00000001000002ce


- Wait for the builds to appear on [the Releases tab on GitHub](https://github.com/zed-industries/zed/releases) (typically takes around 30 minutes)
- Proof-read and edit the release notes as needed.
- Download the artifacts for each release and test that you can run them locally.
- Publish the release.

## Nightly release process

In addition to the public releases, we also have a nightly build that we encourage employees to use.
Nightly is released by cron once a day, and can be shipped as often as you'd like. There are no release notes or announcements, so you can just merge your changes to main and run `./script/trigger-release nightly`.

Title: Completing Releases and Nightly Builds

Summary

After builds are created on GitHub, the release notes should be edited and proof-read. The artifacts need to be downloaded and verified. Finally, the release should be published. In addition to the public releases, nightly builds are also available for internal use. They are released by cron daily without release notes, and can be triggered with a script.