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

Version 3.2.7 #1790

Merged
merged 6 commits into from
Mar 7, 2023
Merged

Version 3.2.7 #1790

merged 6 commits into from
Mar 7, 2023

Conversation

dcorral
Copy link
Contributor

@dcorral dcorral commented Mar 2, 2023

/kind chore

Items

Prerequisites

Previous master commit: f0a33ce8e2f1888e79af7e6ddebf1d9d628158c0

Prepare Version

  • Bump Version (configure.ac)
    • <major>: Planned consensus upgrades and major breaking releases
    • <minor>: Unplanned consensus upgrades and fixes
    • <patch>: Non-breaking releases (API additions are accepted)
  • Major / Minor upgrade-only:
    • Bump Protocol Version (version.h)

Release notes checklist

  • Release type:
    • Mandatory: Consensus
    • Recommended: Significant fixes, index changes, performance, or major additions
    • Optional: Everything else, including minor RPC additions
  • Indexes
    • Reindex mandatory
    • Reindex optional (added features / fixes but node still continues without affecting consensus)
    • Reindex not-needed
  • Document RPC changes since previous release
  • Add release notes as comment below that's to be copied over once release is tagged

Planned release checklist / Post-release checklist

Note: Manual ops that's to be automated eventually after which it's a single checkpoint in pre-req.

All versions

  • Setup node with scratch sync
    • VM: mainnet-ain-scratch-<version>[+flags]
  • Setup node with recent snap
    • VM: mainnet-ain-snap-<height>-<version>[+flags]

If re-index not mandatory:

  • Update rollover node that's been incrementally rolled over from scratch
    • VM: mainnet-ain-rollover-scratch[+flags]
  • Update rollover node from last version from one of it's snapshots
    • VM: mainnet-ain-rollover-snap-<height>[+flags]

Checks

  • Sync to tip (at least till <rel-time-height>+120 blocks)
  • Verify diff checks after across above VMs

Note: <version>: Separated units by _` if dot not allowed

@dcorral
Copy link
Contributor Author

dcorral commented Mar 7, 2023

Recommended Upgrade

  • Performance improvements:
    • Thread pool and concurrency optimizations: (#1788, #1803)
    • Cache getblockchaininfo result (#1791)
    • Remove CLockFreeGuard entirely in subsequent PRs and replace it with standard patterns of std::unique_lock coupled with AtomicMutex. (#1800), (#1797), (#1796)
  • RPC
    • New votegovbatch (#1786)
    • listtransactions Adds previously undocumented output fields (#1785)
  • Fixes

Upgrade Notes

  • For >= 3.2.4, no reindex needed. Drop-in upgrade.
  • For >= 3.2.0 and <= 3.2.3, reindex is recommended, but optional and can be drop-in upgrade.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
  • For all other updates, one of the following is required: a fresh sync, the most recent snapshot.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.

Flag Changes

  • None

RPC Changes

  • New votegovbatch Create multiple voting TXs with a single RPC call.

Network Snapshot

What's Changed

Full Changelog: v3.2.6...v3.2.7

@Bushstar Bushstar merged commit 0edc8e0 into master Mar 7, 2023
@Bushstar Bushstar deleted the dcorral-pr-v3-2-7 branch March 7, 2023 11:15
@prasannavl
Copy link
Member

prasannavl commented Mar 7, 2023

Updated release notes

Key motivations:

  • The immediate section below Upgrade type is for "user centric" information. Helpful summary in simple form of the key updates where necessary.
  • Definitely not: Copy paste of PR info or automated info unless that's absolutely relevant.
  • Non-goal: Capture everything (that's what the below sections are for)
  • Please take extra caution to ensure that "Upgrade Notes" aren't confusing. Get some one else to proof read.
    "Reindex is recommended but optional for people affected by bug X" is both incorrect and adds more confusion.

Recommended Upgrade

  • Stability fixes:
    • Fixes missing tokens on the balance RPCs in edge cases even though consensus level balances were unaffected.
      • Issue: Nodes missed to index a cascaded chain of calculation that resulted from spent governance voting reward tokens
  • Performance improvements:
    • getburninfo calculation is now done in parallel and is memoized on first call. Only the differential heights is recalculated making it much cheaper to be called.
    • Validation of vault liquidation logic is now done in parallel when hardware supports it and should be visible improvements on the sync performance with more hardware cores.

Upgrade Notes

  • For >= 3.2.4, no reindex needed. Drop-in upgrade.
    • Reindex is optional, however recommended for wallets affected by (#1763)
  • For >= 3.2.0 and <= 3.2.3, reindex is recommended, but optional and can be drop-in upgrade.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
  • For all other updates, one of the following is required: a fresh sync, the most recent snapshot.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.

Flag Changes

  • None

RPC Changes

  • Undocumented API for advanced uses only: votegovbatch

Network Snapshot

What's Changed

Full Changelog: v3.2.6...v3.2.7

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.

5 participants