![]() svav: -datadir=/tmp/22-rc-test is used in the Testing-Guide does everyone have their release candidate? Not sure if I can complete it within a session of a review club. But would have to go through the manual testing of each sections, and thats gonna take some time. I have ran basic build and tests for rc2. you can also do a VM, as others are suggesting svav: if you setup the custom data directory, it won't interfere with your existing setup! svav You could also run the new version inside of a Docker container here we are specifying to make sure we can easily clean up later and that we also don't interfere with your regular bitcoin setup svav: I would suggest running virtual machine, like using VirtualBox michaelfolkson: bitcoin core will always setup a data directory, it just uses the default one if you don't specify I don't run a bitcoin node at the moment, but if I did, what is the best way to test the new release without affecting your existing node? Ya it is a great place to start learning a lot of non-code stuffs around core. babasancheti: the pr review club is just IRC going over the guide in the club is a great way to get more people involved with testing, tho raj: ideally, we would have a guide for every major release! the guides are produced independent of the pr review club I never set up command line environment when compiling (or wipe, recreate data dir) :) Testing with no data dir definitely makes sense for some things josibake, I was wondering, does such testing guides for RCs are produced for each release? or only this one for the review club? are we testing on signet or also on mainnet ? we'll give a few minutes for people to get their release candidate, but no need to wait on everyone else if you'd like to start working through the sections or have questions setting up dependencies and compiling can take a long time when it's the first time if you've never compiled from source before, you might want to go with the pre-compiled binary to begin, you'll need to either compile from source or get a pre-compiled binary. ![]() raj: I beleive I've been in clube maybo once. for any newcomers (and just as a reminder), its encouraged to just blurt out questions! no need to ask for permission first or worry about if you're interrupting another question not first time in club, but first time in rc testing. (also, give us a hi if you plan to follow along!) for starters, is this anyone's first time? not only is this a great way to help out bitcoin development by testing, but its also a great way to get experience compiling bitcoin on your own to help us along, we will be following this guide: today we are going to be testing bitcoin's upcoming 22.0 release hello everyone! welcome to another special edition of the bitcoin pr review club The guide is just to get you started on testing, so feel free to read theĪnd bring ideas of other things you’d like to test! You can follow the instructions for setting up the Trezor If you plan to use an emulator, it is recommended you set it up before the.Please note: for this release we will be testing new External Signerįeatures, which will require you to either a) have a hardware wallet or b).This Bitcoin Core Release Candidate TestingĪ tutorial for testing the release candidate. Meeting is for people who want to help with that vital review process. To ensure that users don’t experience issues with the new software, it’sĮssential that the rcs are thoroughly tested. Issues are found in an rc, and that rc is then considered to be the final Merged into the branch and a new rc is tagged. When all of the PRs for a release have been merged, Release Candidate 1 Major versions of Bitcoin Core are released every 6-8 months. Testing Bitcoin Core 22.0 Release Candidates ( tests) Aug 18, 2021
0 Comments
Leave a Reply. |