Skip to content

Conversation

@igor-sirotin
Copy link
Contributor

@igor-sirotin igor-sirotin commented Feb 1, 2026

Propose new Terminology for roadmap

I wasn't asked, but... as a new user of roadmap, it was very unobvious to me why "Milestone" is not a point in time, but rather a group of deliverables, so I came up with this proposal. I don't want to introduce yet another solution, instead I propose to follow common PM practices.

I've kept the changes straightforward. I think this is a good timing for such a change, as it will help to coordinate between components roadmaps and Logos Testnets.

Motivation

  • Current terminology uses "Milestone" ambiguously for both work packages (weeks/months of effort) and zero-duration checkpoints (e.g., "rc.1")
  • Testnets were incorrectly called "milestones" when they're actually versioned releases
  • Inconsistent understanding of how work is structured and tracked

Changes

Key Terminology Updates

Old Term New Term Definition
Milestone (work container) Initiative Top-level work container spanning weeks/months with outcomes, resources, and risks
Testnet vX Release Timeboxed bundle shipped for testing or external use
N/A Milestone (checkpoint) Zero-duration gate inside a release (e.g., "RC freeze", "go-live")
graph LR
    I["Initiative"]
    D["Deliverable"]
    E["Epic"]
    Is["Issue"]
    R["Release"]
    M["Milestone"]
    
    I -->|contains| D
    D -->|contains| E
    E -->|contains| Is
    I -->|included in| R
    R -->|split by| M
Loading

New Fields Introduced

Initiative fields:

  • Monitoring Links
  • Includes in Releases (bidirectional link to releases)
  • FURPS (quality dimensions)

Release fields:

  • Release Window
  • Scope
  • Includes Initiatives (grouped by component)
  • Milestones (optional checkpoints)

Impact

  • Clearer communication across projects about planning scope and timelines
  • Eliminates confusion between work packages and checkpoints
  • Provides structure for cross-team releases (testnets, product launches)

Next Steps

  • Teams review and provide feedback
  • Gradual adoption in new initiatives/releases
  • Prepare an Initiative template
  • Add legacy doc disclaimer where "milestone" means "initiative"

@igor-sirotin igor-sirotin self-assigned this Feb 1, 2026
@igor-sirotin
Copy link
Contributor Author

@kaiserd @corpetty please let me know what you think.
If you're not completely against, then we can request reviews from other teams leads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants