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.

Sign up for GitHub

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

Jump to bottom

Release Process for v21.0 #6081

Open
14 of 55 tasks
PastaPastaPasta opened this issue Jun 25, 2024 · 2 comments
Open
14 of 55 tasks

Release Process for v21.0 #6081

PastaPastaPasta opened this issue Jun 25, 2024 · 2 comments

Comments

@PastaPastaPasta
Copy link
Member

PastaPastaPasta commented Jun 25, 2024 •
edited
Loading

v21.0.0 Release Process

Before every minor and major release:

        consensus.vDeployments[Consensus::DEPLOYMENT_MN_RR].bit = 10;
        consensus.vDeployments[Consensus::DEPLOYMENT_MN_RR].nStartTime = 1704067200;   // January 1, 2024
        consensus.vDeployments[Consensus::DEPLOYMENT_MN_RR].nTimeout = 1767225600; // January 1, 2026

Tag the Release

Check CI

  • Validate that CI passes

Do Guix Build (for unsigned binaries) and create PRs

  • Pasta Guix Build
  • Udjin Guix Build
  • Thephez Guix Build
  • Kittywhiskers Guix Build
  • Knst Guix Build

Create Windows/OS X detached signatures (note: it might be decided skip signed binaries for RCs)
Only once the Windows/OS X builds each have 3 matching signatures may they be signed with their respective release keys.

  • Pasta creates windows detached signature and commits
  • pasta creates OS X detached signature

Update Guix Builds with signed binaries (note: it might be decided skip signed binaries for RCs)

  • Pasta Guix Build
  • Udjin Guix Build
  • Thephez Guix Build
  • Kittywhiskers Guix Build
  • Knst Guix Build

After 3 or more people have guix-built and their results match:

  • Create SHA256SUMS.asc for the builds
  • GPG sign each download / binary
  • Upload zips and installers, as well as SHA256SUMS.asc from last step, to github as github draft release.
  • Validate SHA256SUMS.asc and all binaries attached to github draft release are correct
  • Notarize OS X binaries
  • Release on github
  • Update website
  • Ensure that docker hub images are up to date

Announce the release:

After the release

  • Submit patches to BTCPay to ensure they use latest / compatible version see Release Schedule for v18.0.0 #4211 (comment) (@strophy ?)
  • Fast forward master; merge master into develop
  • Make develop branch the default branch in Github (note this is a potentially breaking change for people who simply clone the repo and build without specifying a branch)

Additional Items

  • Prepare release blog post (necessary so we have a permalink to use on twitter, reddit, etc.)
  • Prepare product brief (major versions only?) (@thephez; need to talk with marina and publish this asap)
  • Prepare a release announcement tweet (tell Marina)
  • Follow-up tweets with any important block heights for consensus changes (Marina again)
  • Post on reddit
  • Update docs (readme and RTD) (@thephez)
  • Test Docker build runs without errors in Dashmate (@shumkov)
  • Add new Release Process items to in repo release process document (@knst)
@thephez
Copy link
Collaborator

thephez commented Jul 17, 2024

@PastaPastaPasta I'm not aware of any changes that are required in bips.md

This was referenced Jul 18, 2024
Merged
Merged
PastaPastaPasta added a commit that referenced this issue Jul 18, 2024
@PastaPastaPasta
Merge #6126: feat: enable EHF activation of MN_RR on mainnet
ea6f411 
a8a3ea0 feat: enable EHF activation of MN_RR on mainnet (Konstantin Akimov)

Pull request description:

  ## Issue being fixed or feature implemented
  #6081

  ## What was done?
  Removed a code, that disabled MN_RR activation with EHF on Main Net

  ## How Has This Been Tested?
  This code is tested on devnet, is in process of testing on testnet.

  ## Breaking Changes
  It make MN_RR possible to get active on mainnet.

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone

ACKs for top commit:
  UdjinM6:
    utACK a8a3ea0
  PastaPastaPasta:
    utACK a8a3ea0

Tree-SHA512: 0ae7aecca8463436e952154210cf564333cd77dd1149f7ff88ca144f3b7c434e75e473ea3a6850da1b126efd8a9cece34e46b4bf2b37f5937bcf1f5780e18f50
PastaPastaPasta added a commit that referenced this issue Jul 18, 2024
@PastaPastaPasta
Merge #6125: docs: update manpages for 21.0
0702f89 
e2f56de docs: update manpages for 21.0 (Konstantin Akimov)

Pull request description:

  ## Issue being fixed or feature implemented
  #6081

  ## What was done?
  run `./contrib/devtools/gen-manpages.sh`, sanitize version name

  ## How Has This Been Tested?
  n/a

  ## Breaking Changes
  n/a

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone

ACKs for top commit:
  UdjinM6:
    utACK e2f56de
  PastaPastaPasta:
    utACK e2f56de

Tree-SHA512: 9b56f7a31279457aed1b7ed0b627d4364f786948f6df3176e24ab73b68d785fc90d9bf6136d7965c1c5b97b589b4d228edd338e666d1999e841c6e544f054c05
PastaPastaPasta added a commit to PastaPastaPasta/dash that referenced this issue Jul 23, 2024
@PastaPastaPasta
Merge dashpay#6125: docs: update manpages for 21.0
e780b3d 
e2f56de docs: update manpages for 21.0 (Konstantin Akimov)

Pull request description:

  ## Issue being fixed or feature implemented
  dashpay#6081

  ## What was done?
  run `./contrib/devtools/gen-manpages.sh`, sanitize version name

  ## How Has This Been Tested?
  n/a

  ## Breaking Changes
  n/a

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone

ACKs for top commit:
  UdjinM6:
    utACK e2f56de
  PastaPastaPasta:
    utACK e2f56de

Tree-SHA512: 9b56f7a31279457aed1b7ed0b627d4364f786948f6df3176e24ab73b68d785fc90d9bf6136d7965c1c5b97b589b4d228edd338e666d1999e841c6e544f054c05
PastaPastaPasta added a commit to PastaPastaPasta/dash that referenced this issue Jul 23, 2024
@PastaPastaPasta
Merge dashpay#6126: feat: enable EHF activation of MN_RR on mainnet
024d272 
a8a3ea0 feat: enable EHF activation of MN_RR on mainnet (Konstantin Akimov)

Pull request description:

  ## Issue being fixed or feature implemented
  dashpay#6081

  ## What was done?
  Removed a code, that disabled MN_RR activation with EHF on Main Net

  ## How Has This Been Tested?
  This code is tested on devnet, is in process of testing on testnet.

  ## Breaking Changes
  It make MN_RR possible to get active on mainnet.

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone

ACKs for top commit:
  UdjinM6:
    utACK a8a3ea0
  PastaPastaPasta:
    utACK a8a3ea0

Tree-SHA512: 0ae7aecca8463436e952154210cf564333cd77dd1149f7ff88ca144f3b7c434e75e473ea3a6850da1b126efd8a9cece34e46b4bf2b37f5937bcf1f5780e18f50
@knst knst mentioned this issue Jul 24, 2024
Merged
5 tasks
PastaPastaPasta added a commit that referenced this issue Jul 24, 2024
@PastaPastaPasta
Merge #6151: chore: update seeds for v21 release
f81000b 
43c3953 chore: update seeds (Konstantin Akimov)
16dd043 chore: added extra onion seeds (provided by pasta) (Konstantin Akimov)

Pull request description:

  ## Issue being fixed or feature implemented
  #6081

  ## What was done?
  Extra onion seeds are provided by pasta.

  ```sh
  dash-cli protx list valid 1 2110129 > protx_list.json

  # Make sure the onion seeds still work!
  while IFS= read -r line
  do
    address=$(echo $line | cut -d':' -f1)
    port=$(echo $line | cut -d':' -f2)
    nc -v -x 127.0.0.1:9050 -z $address $port
  done < "onion_seeds.txt"

  python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt
  python3 generate-seeds.py . > ../../src/chainparamsseeds.h
  ```

  ## How Has This Been Tested?
  n/a

  ## Breaking Changes
  n/a

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [x] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone

ACKs for top commit:
  UdjinM6:
    utACK 43c3953
  PastaPastaPasta:
    utACK 43c3953

Tree-SHA512: 8583f030949c6b26b5410eaa4db4f9b85fbe14bc147083861519d9564ae1fff52716b2d8deb233d30ecfb679e778cb2bb2f0ef3dee392cff1986b004b03d9e1e
PastaPastaPasta added a commit to PastaPastaPasta/dash that referenced this issue Jul 24, 2024
@PastaPastaPasta
Merge dashpay#6151: chore: update seeds for v21 release
6bc60a7 
43c3953 chore: update seeds (Konstantin Akimov)
16dd043 chore: added extra onion seeds (provided by pasta) (Konstantin Akimov)

Pull request description:

  ## Issue being fixed or feature implemented
  dashpay#6081

  ## What was done?
  Extra onion seeds are provided by pasta.

  ```sh
  dash-cli protx list valid 1 2110129 > protx_list.json

  # Make sure the onion seeds still work!
  while IFS= read -r line
  do
    address=$(echo $line | cut -d':' -f1)
    port=$(echo $line | cut -d':' -f2)
    nc -v -x 127.0.0.1:9050 -z $address $port
  done < "onion_seeds.txt"

  python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt
  python3 generate-seeds.py . > ../../src/chainparamsseeds.h
  ```

  ## How Has This Been Tested?
  n/a

  ## Breaking Changes
  n/a

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [x] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone

ACKs for top commit:
  UdjinM6:
    utACK 43c3953
  PastaPastaPasta:
    utACK dashpay@43c3953

Tree-SHA512: 8583f030949c6b26b5410eaa4db4f9b85fbe14bc147083861519d9564ae1fff52716b2d8deb233d30ecfb679e778cb2bb2f0ef3dee392cff1986b004b03d9e1e
@thephez
Copy link
Collaborator

thephez commented Sep 11, 2024

When we add new special transactions, we need to open an issue on the dashcore-lib repo so it gets updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PastaPastaPasta @thephez