Proposal: Story Release Naming Convention

Proposals
1

Story Naming Convention

“There are only two hard things in Computer Science: cache invalidation and naming things.”

This proposal establishes a structured naming convention for Story releases. A consistent and meaningful naming scheme enhances clarity, improves communication, and adds an element of creativity to the release process.

Naming Strategy

Since Story is fundamentally about ꧁IP꧂, we propose using intellectual and artistic references for naming various releases. The existing convention follows literary themes: testnets are named after epic poems (Iliad, Odyssey, Aeneid), while mainnets are named after renowned poets (Homer, Virgil). Building on this foundation, we propose the following scheme:

  • Execution Client Releases – Named after iconic musical compositions
  • Consensus Client Releases – Named after renowned paintings
  • PoC Protocol Releases – Named after legendary painters
  • Story Testnet Releases – Named after epic poems written by the poets associated with mainnet releases
  • Story Mainnet Releases – Named after great poets

This structured approach ensures coherence across all Story releases while celebrating the creative works that define human intellectual property.

19 Likes
2

Release name is ꧁IP꧂, can we propose a few options for the release name and let community vote for that?

6 Likes
4

I suggest we keep the smaller component releases with semantic versioning and when grouping as a big release we use a name,
for example, we prepare a release for execution client v1.1 and consensus client v2.0 and we name the collection of releases when rolling out a famous name, then we roll it out to testnet and then mainnet.

6 Likes