Tracking Issue for cuprated v0.0.1 Molybdenite release

[hinto-janai]

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter.

What

This is a tracking issue for the v0.0.1 Molybdenite release.

Steps

• Changelog
  • Relevent changes are added to misc/changelogs/v${VERSION}.md
• User Book
  • Update necessary documentation
  • Book title reflects cuprated's version
• cuprated
  • --help output to binaries/cuprated/help.txt
  • Killswitch timestamp updated
• Repository
  • Decide specific commit (backup: 7e8e621)
  • Create draft release
  • Create version tag
  • Build CI binaries
  • Collect binary hashes and PGP signatures: cuprated v0.0.1 Molybdenite release signatures #372
• cuprated testing
  • Full-sync from scratch
    • x64 Windows
    • x64 Linux
    • ARM64 macOS
    • ARM64 Linux
• Release
  • Add binaries to release
  • Verify hashes
  • Verify PGP signatures
  • Publish Cuprate/user-book
  • Release
• Release announcements
  • Reddit
  • Matrix

Related

Related links for the initial setting up of the first release of cuprated:

• binaries: cuprate-changelog #369
• workspace: initial release cycle files #370

[SyntheticBird45]

https://matrix.to/#/!zPLCnZSsyeFFxUiqUZ:monero.social/$Gmn0d-IWCDAGyzeyo0CgK0OqXejdc2mx0hQjBDlks3k?via=monero.social&via=matrix.org&via=unredacted.org

const NAME_OF_METAL: &str = "Molybdenite"