release: Bump for 2.0 release cycle. #3269
Conversation
|
Previous dcrd hardforks have only incremented the minor version number. Is there a reason you're planning for 2.0.0 instead of 1.10.0 after 1.9.x? |
|
There will not be a 1.9.0 release. It will be 2.0.0 instead. This is bumping in anticipation of that. |
|
Right, I'm just making sure I understand the reason for the major version increment. Is it solely due to the breaking API changes to the Wire package (because of the Mixing transactions module), or is/are there other reasons for a major version increment this time? |
|
no, api changes don't affect the user-facing version we give to the software. they are decoupled specifically so we can make major module changes without changing our "decred version" (which is shared among all of our core software products), and vice-versa (as seen here). the decision to use 2.0.0 is arbitrary. |
|
(and there was no breaking wire changes between tagged releases of the wire module, only between prerelease untagged versions of wire) |
The upcoming release will be version 2.0.0, so this bumps the development version accordingly.
davecgh
force-pushed
the
release_bump_dev_version
branch
from
9eb65e2 to
3d4d272
Compare
The upcoming release will be version 2.0.0, so this bumps the development version accordingly.