"Versionless" -> "Release Tracks"

[jtcohen6]

What are you changing in this pull request and why?

We are adding new "release tracks" for automatic upgrades of dbt in dbt Cloud:

• "Latest" (renamed from "Versionless")
• "Compatible"
• "Extended"

The following language needs updating:

• When we use "Versionless" to describe the way of receiving ongoing/automatic updates to dbt in dbt Cloud, we should instead say "Release Tracks"
• When we use "Versionless" to describe the continuously updating release track (ahead of dbt Core OSS), we should instead call this "Latest"

I'm also adding a placeholder "Compatible Track Changelog" page, which we will update with each monthly release, starting in December 2024. (I expect the updates will be manual for starters; we can look to automate later.)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	Dec 4, 2024 8:24pm

[matthewshaver]

@jtcohen6 In a few spots, we fluctuate between "Latest" and "Release Tracks." Would it be beneficial to consolidate or combine here? Maybe just "Release Tracks" where "Latest" is or "Latest Release Track" for this reset, at least? We could use "Latest" when tagging items during the release process.

[jtcohen6]

@nataliefiann @matthewshaver Thanks for taking a look!

There's a nuance that feels important to capture:

• "Release tracks" describes the mechanism of automatic upgrades that will be how dbt Cloud customers get ongoing updates going forward.
• When it comes to specific functionality that we've released over the last several months, much of this functionality is available only on the "Latest" release track today. It will be available on the "Compatible" release track only after it's been released in dbt Core v1.9. (That's happening next week.) Customers using "Compatible" should generally look at the docs for the most recent Core release (which will be v1.9 as of next week) to understand what functionality they have access to.

I do like the point of referring to this consistently as "Latest release track" (instead of just "Latest"). I'll do a re-review of the changes now and try to update it everywhere for consistency.

When we actually release Compatible/Extended next week (after the v1.9 final release), I'll plan to swing back with another docs update for:

• Compatible + Extended - coming soon → preview
• 1.9 in version dropdown → customDisplay: "1.9 (Compatible)"

[runleonarun]

fixing build error

[runleonarun]

@matthewshaver I feel like the three releases were hard to understand the differences so I made the paragraphs parallel. You get a continuous, monthly, or delayed release. Feel free to iterate further.

[runleonarun]

Made changes and will follow up with a PR to make capitalization more consistent.