search

dtr-org / unit-e-project

Unit-e project information
MIT License
13 stars 4 forks source link

Define testnet release procedure #116

Closed cornelius closed 5 years ago

cornelius commented 5 years ago

This document describes a very light-weight procedure how testnet releases are done, how it is made clear what is running in the testnet, and how breaking changes are handled and announced.

Signed-off-by: Cornelius Schumacher cornelius@thirdhash.com

castarco commented 5 years ago

Besides my previous comment, I have doubts regarding breaking changes. What about "nodes signalling"?

I know that that's mostly for mainnet, where potentially breaking changes have to be accepted by a super-majority to avoid network splits, but wouldn't make sense also to do that in testnet?

cornelius commented 5 years ago

I know that that's mostly for mainnet, where potentially breaking changes have to be accepted by a super-majority to avoid network splits, but wouldn't make sense also to do that in testnet?

The intention of the document is to cover the current situation where the mainnet still is some time away. We certainly will need more sophisticated procedures the closer we get to that, but for now I think it's best to keep things simple so we can continue to move fast while the impact of breaking changes is still quite low.