GitLab

Release milestone: %v0.12.4

PRE-RELEASE TASKS

ECONOMY PARTNERS UPDATES. Mandatory update, network-wide.

When writing a notification message, put in copy: [email protected], Artem ([email protected]), Fabian ([email protected]), Chris ([email protected]), Dan ([email protected]), Andrew ([email protected]).

• 1. Notify exchanges. Responsible: @defunctec

  • 14 days before release
  • 2 days before release
  • Release day

• Bittrex.com (SLACK)

• Litebit.eu (EMAIL/TICKET)

• c-cex.com (EMAIL/TICKET)

• yobit.com (EMAIL/TICKET)

• BarterDEX (SLACK)

• Coinexchange.io (EMAIL/TICKET)

• CoinPayments.net (EMAIL/TICKET)

• braziliex.com (EMAIL)

• 2. Notify Pools/Miners

  • 14 days before release
    • BTC.TOP (MOST IMPORTANT) @Stonehedge
    • infernopool.com (INFERNOMAN) @defunctec
    • ispace.co.uk (EMAIL/TICKET) @defunctec
    • https://www.mining-dutch.nl/ @defunctec @higherbridge
  • 2 days before release
    • BTC.TOP (MOST IMPORTANT) @Stonehedge
    • infernopool.com (INFERNOMAN) @defunctec
    • ispace.co.uk (EMAIL/TICKET) @defunctec
    • https://www.mining-dutch.nl/ @defunctec @higherbridge
  • Release day
    • BTC.TOP (MOST IMPORTANT) @Stonehedge
    • infernopool.com (INFERNOMAN) @defunctec
    • ispace.co.uk (EMAIL/TICKET) @defunctec
    • https://www.mining-dutch.nl/ @defunctec @higherbridge

• 3. Notify block explorers. Responsible: @defunctec

  • 2 days before release
  • Release day
  • chainz.cryptoid.info (EMAIL/TICKET)
  • ex.crownlab.eu (@Stonehedge)
  • coinmarketcap.com (EMAIL/TICKET)
  • coingecko.com (EMAIL/TICKET)
  • coincap.io (EMAIL/TICKET)
  • crw2-bitcore.crown.tech (@zhanzhenzhen)

• 4. Notify block explorers. Responsible: @defunctec

  • 2 days before release
  • Release day
  • chainz.cryptoid.info (EMAIL/TICKET)
  • ex.crownlab.eu (@Stonehedge)
  • coinmarketcap.com (EMAIL/TICKET)
  • coingecko.com (EMAIL/TICKET)
  • coincap.io (EMAIL/TICKET)
  • crw2-bitcore.crown.tech (@zhanzhenzhen)

• 5. Notify stores/merchants. Responsible: @defunctec

  • 2 days before release
  • Release day
  • Welto.io (EMAIL/TICKET)
  • cryptothreads.org (@Snoops)

• 6. Notify Hosting. Responsible: @defunctec

  • 2 days before release
  • Release day
  • node-vps.com
  • nodesupply.com
  • crownvps.com
  • mymasternode.com

• 7. Notify Statistic Sites. Responsible: @defunctec

  • 2 days before release
  • Release day
  • crown.today (MATTBLLACK)
  • crowncentral.net (LUCD)
  • Masternodes.pro (EMAIL/TICKET)
  • mnrank.com (EMAIL/TICKET)
  • masternodes.online (EMAIL/TICKET)

CORE TASKS

• 5. Make decision about the enforcement feature. Responsible: @artem, @ashot, chaositec

  • 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 20 days to make sure everybody is updated.

• 6. Fix update scripts. Responsible: @ashot, @defunctec, @Stonehedge

  • Edit existing scripts to account for changes in the code (DEFUNCTEC/LUCD/STONEHEDGE)
  • Distribute and update all links to scripts (DEFUNCTEC/LUCD/STONEHEDGE)
  • Masternode/Sytemnode/testnet scripts (DEFUNCTEC/LUCD/STONEHEDGE)
    Update this step after issue #111 (closed) is finished

• 6. DNS Seed Nodes. Responsible: @dzlbobo, @hypermist, DevOps team

  • Update Seed nodes to the latest client

• 7. ElectrumX Nodes. Responsible: @hypermist, DevOps team

  • Update all electrum servers to the latest client

• 8. Make Official Announcements

  • Is the Update mandatory or not?
  • Post to bitcointalk with all links to wallets. (@defunctec, @Snoops)
  • Update the original/opening post on bitcointalk with new links to the wallet. (@defunctec, @Snoops JELIMAN)
  • Update all the translated posts on bitcointalk. (@Crownfan)
  • Post to https://forum.crown.tech with the links to the wallet (@Twister, @higherbridge)
  • Post update to social media (@Snoops)
  • Send emails to all ZenDesk users (@Crownfan)

• 9. Community Support

  • Update tutorial pdf with the latest changes (@defunctec, @higherbridge)
  • Update YouTube tutorial videos with the latest changes (@higherbridge, @Twister, MATTBLACK)
  • Create Release Notes document for marketing/support team, use GitLab milestone release notes, %"milestone name" (@dzlbobo, @artem)