-
Notifications
You must be signed in to change notification settings - Fork 36.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release schedule for 0.18.0 #14438
Comments
|
If #12255 gets merged before this next release, distro package maintainers should be notified of the correction of the default data directory. |
There should probably be a 0.17.2 release before the 0.18.0 release |
What's the primary motivation for 0.17.2? |
There have been some minor fixes, but I see that that might not be enough motivation to do it before 0.18.0 |
☃️Feature freeze is today / tomorrow depending on where you are. |
Feature freeze is now in effect, we'll only merge bugfixes until the 0.18 split-off. |
🌱 The |
|
Release notes for 0.18.0 can be edited on the wiki now, as usual for major versions in RC-phase: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.18.0-Release-Notes-Draft |
|
|
Testing feedback can go here: #15555 |
|
0.18.0rc2 test binaries are now available. |
0.18.0rc3 test binaries are now available. |
0.18.0rc4 test binaries are now available. |
🚀 |
Here is a proposed release schedule for 0.18.0, the next major release of Bitcoin Core. Like for previous major releases I've aimed for a release 6 months after the last (#12624).
2019-02-01 ✔️
2019-02-15 ✔️
2019-03-01 ✔️
0.18
branch frommaster
0.18.0rc1
2019-04-03 ✔️
If any specific dates or timeframes are a problem for you, let me know.
The text was updated successfully, but these errors were encountered: