@@ -291,24 +291,48 @@ bitcoin.org (see below for bitcoin.org update instructions).
291
291
- After the pull request is merged, the website will automatically show the newest version within 15 minutes, as well
292
292
as update the OS download links. Ping @saivann /@harding (saivann/harding on Freenode) in case anything goes wrong
293
293
294
- - Announce the release:
295
-
296
- - bitcoin-dev and bitcoin-core-dev mailing list
297
-
298
- - Bitcoin Core announcements list https://bitcoincore.org/en/list/announcements/join/
294
+ - Update other repositories and websites for new version
299
295
300
296
- bitcoincore.org blog post
301
297
302
298
- bitcoincore.org RPC documentation update
303
299
304
- - Update title of #bitcoin on Freenode IRC
300
+ - Update packaging repo
305
301
306
- - Optionally twitter, reddit /r/Bitcoin, ... but this will usually sort out itself
302
+ - Notify BlueMatt so that he can start building [ the PPAs] ( https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin )
303
+
304
+ - Create a new branch for the major release "0.xx" (used to build the snap package)
305
+
306
+ - Notify MarcoFalke so that he can start building the snap package
307
+
308
+ - https://code.launchpad.net/~bitcoin-core/bitcoin-core-snap/+git/packaging (Click "Import Now" to fetch the branch)
309
+ - https://code.launchpad.net/~bitcoin-core/bitcoin-core-snap/+git/packaging/+ref/0.xx (Click "Create snap package")
310
+ - Name it "bitcoin-core-snap-0.xx"
311
+ - Leave owner and series as-is
312
+ - Select architectures that are compiled via gitian
313
+ - Leave "automatically build when branch changes" unticked
314
+ - Tick "automatically upload to store"
315
+ - Put "bitcoin-core" in the registered store package name field
316
+ - Tick the "edge" box
317
+ - Put "0.xx" in the track field
318
+ - Click "create snap package"
319
+ - Click "Request builds" for every new release on this branch (after updating the snapcraft.yml in the branch to reflect the latest gitian results)
320
+ - Promote release on https://snapcraft.io/bitcoin-core/releases if it passes sanity checks
307
321
308
- - Notify BlueMatt so that he can start building [ the PPAs ] ( https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin )
322
+ - This repo
309
323
310
- - Archive release notes for the new version to ` doc/release-notes/ ` (branch ` master ` and branch of the release)
324
+ - Archive release notes for the new version to ` doc/release-notes/ ` (branch ` master ` and branch of the release)
311
325
312
- - Create a [ new GitHub release] ( https://github.com/bitcoin/bitcoin/releases/new ) with a link to the archived release notes.
326
+ - Create a [ new GitHub release] ( https://github.com/bitcoin/bitcoin/releases/new ) with a link to the archived release notes.
327
+
328
+ - Announce the release:
329
+
330
+ - bitcoin-dev and bitcoin-core-dev mailing list
331
+
332
+ - Bitcoin Core announcements list https://bitcoincore.org/en/list/announcements/join/
333
+
334
+ - Update title of #bitcoin on Freenode IRC
335
+
336
+ - Optionally twitter, reddit /r/Bitcoin, ... but this will usually sort out itself
313
337
314
338
- Celebrate
0 commit comments