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

Release Process for v20.0.0 #5694

Open
37 of 47 tasks
PastaPastaPasta opened this issue Nov 13, 2023 · 4 comments
Open
37 of 47 tasks

Release Process for v20.0.0 #5694

PastaPastaPasta opened this issue Nov 13, 2023 · 4 comments

Comments

@PastaPastaPasta
Copy link
Member

PastaPastaPasta commented Nov 13, 2023

v20.0.0 Release Process

Before every minor and major release:

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 Gitian 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 gitian-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 (we can't do this) (talk to @tikhop (pavel) about this
  • Release on github
  • Update website
  • Ensure that docker hub images are up to date

Announce the release:

After the release

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 Nov 13, 2023

@PastaPastaPasta The product brief was published last week on the Dash blog

@ogabrielides
Copy link
Collaborator

Reindexed both Mainnet and Tesnet successfully with -assumevalid=0

@thephez
Copy link
Collaborator

thephez commented Nov 14, 2023

Updated user docs
Updated core docs

PastaPastaPasta pushed a commit that referenced this issue Nov 29, 2023
## Issue being fixed or feature implemented
Our [Release Process document](doc/release-process.md) is not exactly
matched with our [template
issue](#5694) that created by
copy-paste from previous release.

For the next release just copy test from this document to new issue

## What was done?
[Release Process document](doc/release-process.md) is updated to match
with our real release process.
This document has also detailed instructions for many steps (in compare
to the issue that we use now which is more checklist) to make releasing
process easier for all participant.

## How Has This Been Tested?
Tested on air by 2 last released: v19, v20:
#5694

## 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

---------

Co-authored-by: thephez <[email protected]>
Co-authored-by: UdjinM6 <[email protected]>
@strophy
Copy link

strophy commented Dec 15, 2023

BTCPayServer:

Thanks @ktechmidas

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

No branches or pull requests

4 participants