Skip to content

GitLab

Closed
Created by J. Herranz@CrownfanReporter35 of 89 tasks completed35/89 tasks

Release Tasks v 0.13.0

Release date: 28.03.2019

PRE-RELEASE TASKS

ECONOMY PARTNERS UPDATES. Mandatory update, network-wide.

When writing a notification message, put in copy: [email protected], Artem ([email protected]), Jose([email protected]), [[email protected]]

CORE TASKS

  • 5. Make decision about the enforcement feature. Responsible: @ashot @presstab

    • Reach social consensus among the team members with regard to enforcement. If there are changes in the consensus rules, then the enforcement feature for masternode/systemnode payments, budget & superblock must be turned off 1 hour before the release using spork keys (spork keys should be available to multiple team members using solution from #119).

    • Turn the enforcement off.

    • Keep the enforcement off for 14 days to make sure everybody is updated.

  • 6. Fix update scripts. Responsible: @ashot

  • 7. DNS Seed Nodes. Responsible: @ashot @Edwardmorra

    • Update Seed nodes to the latest client

  • 8. ElectrumX Nodes. Responsible: @ashot @Edwardmorra

    • Update all electrum servers to the latest client

  • 9. Make Official Announcements @Crownfan

    • Is the Update mandatory or not?

    • Post to bitcointalk with all links to wallets. (@crowncoin_knight)

    • Update the original/opening post on bitcointalk with new links to the wallet. (JELIMAN)

    • Update all the translated posts on bitcointalk. (?)

    • Post to https://forum.crown.tech with the links to the wallet (@Edwardmorra @Crownfan )

    • Post update to social media (@Crownfan )

  • 10. Community Support

    • Update tutorial pdf with the latest changes (?)

    • Update YouTube tutorial videos with the latest changes (?)

    • Create Release Notes document for marketing/support team, use GitLab milestone release notes, %"milestone name" (@Crownfan @ashot )

POST-RELEASE TASKS

  • 1. Make sure all the partners have updated their software. Send reminder emails after the update is released, at the following interval (days after release date): 5, 10, 19, 20 Responsible: @Edwardmorra @Crownfan @Sukhovirska @artem

    • Bittrex.com

    • Litebit.eu

    • CoinPayments.net

    • crypto-bridge.com

    • cryptrade.io @lezlaig

    • Zpool.ca

    • Fred

    • chainz.cryptoid.info

    • coinmarketcap.com @crowncoin_knight

    • coingecko.com

    • coincap.io

    • Coinomi @Crownfan

    • Android Crown Node Monitor (CALNAUGHTONJNR)

    • Iphone Masternode Monitor (CALNAUGHTONJNR)

    • Crown price ticker (chrome) (CALNAUGHTONJNR)

    • crown.today (MATTBLACK)

    • crowncentral.net (LUCD)

    • mnrank.com @crowncoin_knight

    • masternodes.online (CryptoSandwich)

  • 2. Turn the enforcement feature back on if necessary 14 days after the release. Responsible: @artem, @ashot,

  • 3. Testing & Feedback. Responsible: @walkjivefly @defunctec

    • Create a forum section for community "bugs" to be created per release
Edited by Mark Brooker
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information