Skip to content

GitLab

Last edited by Josh Wilcox
Page history
This is an old version of this page. You can view the most recent version or browse the history.

pre release post release tasks

PRE-RELEASE & POST-RELEASE TASKS

Release milestone: %"MILESTONE NAME"

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

  • 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)

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

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

  • 3. Notify Applications. Responsible: @defunctec

    • 2 days before release
    • Release day
    • Android wallet (@hypermist)
    • Iphone wallet (@hypermist)
    • Android Crown Node Monitor (CALNAUGHTONJNR)
    • Iphone Masternode Monitor (CALNAUGHTONJNR)
    • Crown price ticker (chrome) (CALNAUGHTONJNR)

  • 4. 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

  • 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)

POST-RELEASE TASKS

  • 1. Make sure all the partners have updated their software. Responsible: @defunctec

    • Bittrex.com
    • Litebit.eu
    • c-cex.com
    • yobit.com
    • BarterDEX
    • Coinexchange.io
    • CoinPayments.net
    • braziliex.com
    • BTC.TOP (MOST IMPORTANT @Stonehedge)
    • infernopool.com
    • ispace.co.uk
    • chainz.cryptoid.info
    • ex.crownlab.eu (@Stonehedge)
    • coinmarketcap.com
    • coingecko.com
    • coincap.io
    • Welto.io
    • cryptothreads.org (@Snoops)
    • Android wallet (@hypermist)
    • Iphone wallet (@hypermist)
    • Android Crown Node Monitor (CALNAUGHTONJNR)
    • Iphone Masternode Monitor (CALNAUGHTONJNR)
    • Crown price ticker (chrome) (CALNAUGHTONJNR)
    • crown.today (MATTBLLACK)
    • crowncentral.net (LUCD)
    • Masternodes.pro
    • mnrank.com
    • masternodes.online

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

  • 3. Testing & Feedback. Responsible: @Crownfan, @Edwardmorra

    • Create bug tickets in ZenDesk
    • Create a forum section for community "bugs" to be created per release