Selendra Release checklist v0.1.2

[LayNath242]

Release Checklist

This is the release checklist for Selendra new version. All following
checks should be completed before publishing a new release of the
Selendra runtime or client.

Runtime Releases

These checks should be performed on the codebase prior to forking to a release-candidate branch.

• Verify spec_version has been incremented since the last release for any native runtimes from any existing use on public (non-private) networks. If the runtime was published (release or pre-release), either the spec_version or impl must be bumped.

• Verify previously completed migrations are removed for any public (non-private/test) networks.

• Verify pallet and extrinsic ordering has stayed the same. Bump transaction_version if not.

• Verify new extrinsics have been correctly whitelisted/blacklisted for
  proxy filters.

• Verify benchmarks have been updated for any modified
  runtime logic.

The following checks can be performed after we have forked off to the release-
candidate branch or started an additional release candidate branch (rc-2, rc-3, etc)

• Verify new migrations complete successfully, and the runtime state is correctly updated for any public (non-private/test) networks development
• Push runtime upgrade to Selendra testnet and verify network stability.

All Releases

• Check that the new client versions have run on the network
  without issue for 12+ hours on >75% of our validator nodes.
• Check that a draft release has been created at
  https://github.com/selendra/selendra/releases with relevant release
  notes
• Check that build artifacts have been added to the draft-release
• Check that all items listed in the milestone are included in the release.