File tree Expand file tree Collapse file tree 1 file changed +1
-20
lines changed Expand file tree Collapse file tree 1 file changed +1
-20
lines changed Original file line number Diff line number Diff line change @@ -271,26 +271,7 @@ cat "$VERSION"/*/all.SHA256SUMS.asc > SHA256SUMS.asc
271
271
272
272
- Push the flatpak to flathub, e.g. https://github.com/flathub/org.bitcoincore.bitcoin-qt/pull/2
273
273
274
- - Push the latest version to master (if applicable), e.g. https://github.com/bitcoin-core/packaging/pull/32
275
-
276
- - Create a new branch for the major release " 0.xx" from master (used to build the snap package) and request the
277
- track (if applicable), e.g. https://forum.snapcraft.io/t/track-request-for-bitcoin-core-snap/10112/7
278
-
279
- - Notify MarcoFalke so that he can start building the snap package
280
-
281
- - https://code.launchpad.net/~bitcoin-core/bitcoin-core-snap/+git/packaging (Click " Import Now" to fetch the branch)
282
- - https://code.launchpad.net/~bitcoin-core/bitcoin-core-snap/+git/packaging/+ref/0.xx (Click " Create snap package" )
283
- - Name it " bitcoin-core-snap-0.xx"
284
- - Leave owner and series as-is
285
- - Select architectures that are compiled via guix
286
- - Leave " automatically build when branch changes" unticked
287
- - Tick " automatically upload to store"
288
- - Put " bitcoin-core" in the registered store package name field
289
- - Tick the " edge" box
290
- - Put " 0.xx" in the track field
291
- - Click " create snap package"
292
- - Click " Request builds" for every new release on this branch (after updating the snapcraft.yml in the branch to reflect the latest guix results)
293
- - Promote release on https://snapcraft.io/bitcoin-core/releases if it passes sanity checks
274
+ - Push the snap, see https://github.com/bitcoin-core/packaging/blob/master/snap/build.md
294
275
295
276
- This repo
296
277
You can’t perform that action at this time.
0 commit comments