Lines Matching refs:release
137 2. Compose a release announcement. Most of the release announcement
145 vi RELEASE_NOTES # update version number and release date
162 The result will be a release artifact that should be used for
168 5. From another host, test the link in the release announcement by
170 checksum. Checking all other links in the release announcement is
180 8. Plug the SHA256 checksum into the release announcement.
182 9. PGP-sign the release announcement text using ``gpg --clearsign``.
185 allows a signed release announcement to be resent via email or sent
188 10. At this point, the release can and should be considered
189 finalized. To commit the release-engineering-related changes to
195 11. Send the PGP-signed release announcement to the following
209 Note: Thunderbird sometimes mangles the PGP-signed release
213 handle this situation correctly. Testing the release announcement
218 to announce the new release (see ``docs/news.rst`` and