Skip to content

Instantly share code, notes, and snippets.

@richardlau
Last active September 2, 2025 14:46
Show Gist options
  • Select an option

  • Save richardlau/c4a1cc362bff95777917ded762742b2c to your computer and use it in GitHub Desktop.

Select an option

Save richardlau/c4a1cc362bff95777917ded762742b2c to your computer and use it in GitHub Desktop.
---
displayMode: compact
---
gantt
  title Release schedule
  dateFormat YYYY-MM-DD
  section main
    Unstable :a1,2024-09-01,2028-04-30
  section Node.js 24
    Current :24current,2025-04-22,until 24active
    Active :active,24active,2025-10-28,until 24maintenance
    Maintenance :crit,24maintenance,2026-10-20,2028-04-30
  section Node.js 23
    Current :23current,2024-10-15,until 23maintenance
    Maintenance :crit,23maintenance,2025-04-01,2025-06-01
  section Node.js 22
    Current :22current,2024-09-01,until 22active
    Active :active,22active,2024-10-29,until 22maintenance
    Maintenance :crit,22maintenance,2025-10-21,2027-04-30
  section Node.js 20
    Active :active,20active,2024-09-01,until 20maintenance
    Maintenance :crit,20maintenance,2024-10-22,2026-04-30
  section Node.js 18
    Maintenance :crit,18maintenance,2024-09-01,2025-04-30
Loading
@marco-ippolito
Copy link

should w add EOL after maintainance? else looks good

@richardlau
Copy link
Author

should w add EOL after maintainance? else looks good

What are you thinking of? This follows the existing https://github.com/nodejs/Release/raw/main/schedule.svg where the bars just stop.

I'm also (ab)using the active and crit tags (https://mermaid.js.org/syntax/gantt.html#syntax) to visually separate the phases-- other tags are done and milestone but I forget how those are rendered by default.

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