-
Notifications
You must be signed in to change notification settings - Fork 292
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
mining: Introduce v2 module. #1831
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was slightly confused at first because GitHub is showing the main module freeze after updating the mining module to use the latest versions of its dependencies, but verifying on git showed the correct order of commits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
This freezes the root module usage of the mining module by removing the replacement and bumping the required version. This means building the software will still produce binaries based on the v1 module until the v2 module is fully released. All future releases will be moving to version 2 of the module. Consequently, it bumps the required module versions as follows: - github.com/decred/dcrd/blockchain@v1.2.0 - github.com/decred/dcrd/mining@v1.1.1
This udpates the mining module to use the lastest module major versions. The updated direct dependencies are as follows: - github.com/decred/dcrd/blockchain/stake/v2@v2.0.1 - github.com/decred/dcrd/blockchain/v2@v2.0.0 - github.com/decred/dcrd/dcrutil/v2@v2.0.0
b12fbca
to
ab6f316
Compare
@matheusd Thanks, I updated the timestamps to remedy that. |
In order to make use of
blockchain/v2
,blockchain/stake/v2
, anddcrutil/v2
, a new major version of themining
module is required becausemining/v1
accepts and returns types from all of them in its API.Consequently, this introduces
mining/v2
. A series of individual commits is provided to make the review process easier. Each commit message more thoroughly describes its purpose, but primarily they consist of the following:mining
module usemining
replace so building the software will still produce binaries based on thev1
module until thev2
module is fully releasedblockchain/stake/v2@v2.0.1
blockchain/v2@v2.0.0
dcrutil/v2@v2.0.0
v2
Finally, it should also be noted that this only introduces the new module and does not update anything to make use of it yet, so building the software will still produce binaries based on the
v1
module.