public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: fanquake <fanquake@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Bitcoin Core 30.0 release candidate is available
Date: Fri, 12 Sep 2025 03:11:26 -0700 (PDT)	[thread overview]
Message-ID: <59c9b53c-7c02-47c8-943d-9a8ac0a1caedn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]

Binaries for Bitcoin Core version v30.0rc1 are available from: 

https://bitcoincore.org/bin/bitcoin-core-30.0/test.rc1/ 

Source code can be found under the signed tag

https://github.com/bitcoin/bitcoin/tree/v30.0rc1

This is a release candidate for a new major version release. 

Preliminary release notes for the release can be found 
here: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/v30.0-Release-Notes-Draft

There is also a testing guide 
here: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/30.0-Release-Candidate-Testing-Guide

Please put your issues or comments 
here: https://github.com/bitcoin/bitcoin/issues/33368

Release candidates are test versions for releases. When no critical 
problems are found, this release candidate will be tagged as v30.0.

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/59c9b53c-7c02-47c8-943d-9a8ac0a1caedn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1501 bytes --]

                 reply	other threads:[~2025-09-12 10:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=59c9b53c-7c02-47c8-943d-9a8ac0a1caedn@googlegroups.com \
    --to=fanquake@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox