Closed bestbeforetoday closed 1 month ago
@denyeart on your suggestion of using different branches for different major versions, this change replaces the v1 implementation at the repository root with the v2 implementation. I've tried it out in my own fork and chaincode resolves the v2.x versions in this location fine. In this repository I don't plan to continue with any more v1 releases, but if that turns out to be necessary then we can create a branch from the state prior to this commit and tag new v1 releases in that branch.
This has a nice side-effect of providing a clear diff of the v1 and v2 implementation at the repository root, which was missing when the two coexisted at the root and v2 subdirectories.
If any further v1 releases are required, they will be made from a maintenance branch taken from the previous commit.