Release tracking PR - v0.30.0

[tcharding]

Add changelog notes and bump the version number to v0.30.0.

TODO - pre-merge

• Release bitcoin_hashes 0.12: release bitcoin_hashes 0.12 #1694
• Release secp 0.27: Bump version to 0.27.0 rust-secp256k1#588
  • Bump secp256k1-sys to v0.8.1 rust-secp256k1#590
• Update secp256k1 dependency to use newly released v0.27: update rust-secp to 0.27.0 #1714
• Merge
  • Remove schemars pin from manifest #1696
  • fix clippy lint #1695
  • Run cargo fmt in CI #1111
• If time permits merge these:
  • Support weight prediction in const context #1710
  • Avoid usage of atomic types if not supported by the target arch #1705
  • Swap out Work::log2 implementation for U256::to_f64 #1713
• Set the release date in changelog header
• And merge these:
  • Mark Denomination as non_exhaustive #1721
  • Feature: Add difficulty_float method for block::Header. #1720
  • Update testing section #1719
  • Remove extern crate hashbrown #1717

TODO - post release

• Release the blogpost: Add a release 0.30 blog post www.rust-bitcoin.org#2
  • Set the date in the blog post to match the date 0.30 is released

[tcharding]

Force pushed some more changelog notes re updating dependencies we control.

[Kixunil]

Note for Optech: should be published after this is merged and the crate is out. Should be soon.

[apoelstra]

@tcharding would you be willing to open a PR to do the actual update?

[apoelstra]

Oh, never mind, this is the PR -- except we just need a PR to update the rust-secp dep. I can do that.

[apoelstra]

Done: #1714

[tcharding]

Are we happy with the taproot API improvements under the "API improvements" header and not in their own section? (Mentioning because we just added a separate taproot section to the blog post.)

[tcharding]

@apoelstra I've set the date to Sunday the 19th March so if we release in the next day or two the "set date" checkbox in PR description can be considered done.

[Kixunil]

Are we happy with the taproot API improvements under the "API improvements" header and not in their own section? (Mentioning because we just added a separate taproot section to the blog post.)

If you mean in changelog then yes, they don't have to be the same.

[tcharding]

Force push is just the mentions of ScriptBuf.

[tcharding]

Rebased on master and added initial link to the new website. Used direct link to blogpost. We have a chicken and egg problem with the blog post and changelog now, we (I) want to add links to online docs to the blog post which implies code released (changelog notes released) which link to the blogpost.

[Kixunil]

IMO start by releasing blog first because less people will accidentally stumble upon it.

[tcharding]

Aight, I rekon we are good to pull the trigger then - either @apoelstra to do it (blogpost and crate release) or I can be online to do it with you Andrew at normal time. I'm getting pretty excited about this release FTR.

[tcharding]

Bother, too excited it would seem. We still need to merge #1714 and then rebase this one.

[apoelstra]

@tcharding #1714 is merged. We are good to go here.

[tcharding]

Updated the release date in changelog to 21st

[apoelstra]

ACK 99d8169

[tcharding]

Needs an ack from you @Kixunil!

[tcharding]

Perhaps give @sanket1729 a chance to ack as well?

[sanket1729]

reACK ffee8ad

[tcharding]

reack please @sanket1729 and @Kixunil if you are still about - I rekon we can still get this out today!

[Kixunil]

ACK ffee8ad

[apoelstra]

ACK ffee8ad

[tcharding]

Wo ho ho, getting close ...

[apoelstra]

Just started merge process. should be less than 30 minutes.

[tcharding]

Can you merge the blog post PR now then? I can deploy if you like (if I do it then I can fix it if its not working :)

[tcharding]

In order for the blog post to be live when we release I'm going to deploy it now.

EDIT: Oh I misread "merge process" as "release process", is there another step before you publish to crates.io? I have not deployed the site yet.

[apoelstra]

@tcharding yes, the remaining thing to do is merge this PR :). But I have to run my CI job on the merge commit before I can do that.

[sanket1729]

Let's go!!!

[apoelstra]

@sanket1729 sorry, we have one more thing to fix :) the readme key in Cargo.toml needs us to add a ../ because we moved the workspace.

Tobin will PR, then if we can quickl ACK (I won't bother doing any tests) we should be able to push in a few minutes.

[tcharding]

#1723

[apoelstra]

And we're live!

[sanket1729]

Is the website also up? I would like tweet about the release.

[tcharding]

I've borked the website, trying to fix now ...

[sanket1729]

Wohoo. Seems to be up now https://rust-bitcoin.github.io/blog/release-0.30.0/

[apoelstra]

Looks like a 404 to me

[tcharding]

yeah I have no idea why. I've hard reset to same commit as was up before and settings in https://github.com/rust-bitcoin/rust-bitcoin.github.io/settings/pages look correct

[tcharding]

Looks like its stuck in githubs github pages build system

[tcharding]

Its through their build system now but 404 still

[tcharding]

It was up the whole time, cache on my machine was returning the 404

[tcharding]

face palm, still 404 - this is working: https://rust-bitcoin.github.io/index.html

[tcharding]

We are live yo! https://rust-bitcoin.org/blog