Standard release process

keep-network / keep-core

The smart contracts and reference client behind the Keep network

https://keep.network

MIT License

121 stars 75 forks source link

Standard release process #947

Open sthompson22 opened 5 years ago

sthompson22 commented 5 years ago

Intro

We'll continue to iterate on the beacon after launch. We need a way to bless and deploy that work whether it's keep-client or contract changes.

What

Where are we going to publish release images?
Who is signing release images?
How do we handle contract migrations (Circle job?)
How/Where do we communicate releases and changelog?
What do we do if something goes sideways?
When do we decide to release?

mhluongo commented 4 years ago

From other discussion

How do I get a clean executable? GitHub releases? What if GH is down?

Originally posted by @mhluongo in https://github.com/keep-network/keep-core/pull/1310/files

This is still an open topic AFAIK, my assumptions are:

We'll provide a Docker image on Docker Hub and or Google Container Registry

We'll have instructions on compiling from source

Originally posted by @sthompson22 in https://github.com/keep-network/keep-core/pull/1310/files

mhluongo commented 4 years ago

@sthompson22 if you aren't familiar, check out the Bitcoin release process. It has some cruft and they are targeting different platforms, but the core ideas around trust should apply here.

I'd like to avoid having a "Keep team" signing key, and instead rely on signatures from team members that can be verified against Keybase.

sthompson22 commented 4 years ago

if you aren't familiar, check out the Bitcoin release process.

:eyes: thanks