[RELEASING.md] Update instructions: new tests, update BoringSSL
Change-Id: I2a613514a6512fdde7bd15c03ce415676a9e558e
diff --git a/RELEASING.md b/RELEASING.md
index bb7fa40..74f7433 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -9,20 +9,26 @@
This document describes steps to follow when releasing a new version of Mundane.
-1. Update `boringssl/boringssl.rs`:
- - Update the `link` attribute at the top of the file to be of the form
- `#[link(name = crypto_x_y_z)]`, where the version to be released is x.y.z.
- where x.y.z is the vers
- - Update the `link_name` attributes - each attribute should be of the form
- `#[link_name = "__RUST_MUNDANE_X_Y_Z_SYMBOL_NAME"]`, where the version to be
- released is version X.Y.Z, and `SYMBOL_NAME` is the name of the symbol that
- the `link_name` attribute is attached to.
-2. Run the `boringssl/test_symbol_conflict.sh` script, and ensure that it
+1. Update `Cargo.toml` with the new version number
+2. Update the `#![doc(html_root_url = ...)]` attribute in `src/lib.rs` to use
+ the new version number
+3. Update `boringssl/boringssl` by running `git submodule foreach git pull
+ origin master`
+4. Update `boringssl/boringssl.rs`:
+ - Run `boringssl/bindgen.sh <major> <minor> <patch>`
+ - Run `git diff` to verify that all of the version numbers have been updated
+ correctly (namely, the `link` attribute at the top of the file is of the
+ form `#[link(name = crypto_X_Y_Z)]`, and every `link_name` attribute is of
+ the form `#[link_name = "__RUST_MUNDANE_X_Y_Z_SYMBOL_NAME"]`, where `X.Y.Z`
+ is the version number, and `SYMBOL_NAME` is the name of the symbol that the
+ `link_name` attribute is attached to)
+ - Run `boringssl/test_symbol_version_name.sh <major> <minor> <patch>` to
+ verify that all of the version numbers have been updated correctly
+5. Run the `boringssl/test_symbol_conflict.sh` script, and ensure that it
passes.
-3. Make sure `cargo test --all-features` passes.
-4. Update the version number in `Cargo.toml`.
-5. Update `CHANGELOG.md` - move any unreleased changes into a new section for
+6. Make sure `cargo test --all-features` passes.
+7. Update `CHANGELOG.md` - move any unreleased changes into a new section for
the new version.
-6. Dry run by running `cargo publish --dry-run --allow-dirty`.
-7. Commit the changes.
-8. Once the changes have been committed, publish by running `cargo publish`.
\ No newline at end of file
+8. Dry run by running `cargo publish --dry-run --allow-dirty`.
+9. Commit the changes.
+10. Once the changes have been committed, publish by running `cargo publish`.
\ No newline at end of file
