Skip to content
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

Merged
merged 4 commits into from
Aug 12, 2019
Merged

Conversation

davecgh
Copy link
Member

@davecgh davecgh commented Aug 10, 2019

In order to make use of blockchain/v2, blockchain/stake/v2, and dcrutil/v2, a new major version of the mining module is required because mining/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:

  • Freeze version 1 of the mining module use
  • Remove the root module mining replace so building the software will still produce binaries based on the v1 module until the v2 module is fully released
  • Update to use the following deps:
    • blockchain/stake/v2@v2.0.1
    • blockchain/v2@v2.0.0
    • dcrutil/v2@v2.0.0
  • Bump the module version to v2
  • Update docs for the new module version

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.

@davecgh davecgh added this to the 1.5.0 milestone Aug 10, 2019
@davecgh davecgh changed the title Mining introduce v2 mining: Introduce v2 module. Aug 10, 2019
Copy link
Member

@matheusd matheusd left a 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.

Copy link
Member

@dnldd dnldd left a 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
@davecgh
Copy link
Member Author

davecgh commented Aug 12, 2019

@matheusd Thanks, I updated the timestamps to remedy that.

@davecgh davecgh merged commit ab6f316 into decred:master Aug 12, 2019
@davecgh davecgh deleted the mining_introduce_v2 branch August 12, 2019 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants