Jeff Baxter

Very candidly, that does become a challenge to maintain that full level of support and patches and QA testing and testing against everything else for 10 different simultaneous major releases.

So, the compromise that we made to be quite candid was we want to be do all the QA have every major release come out being a fully production ready version.

So I want to be very clear on that.

The non LTS versus LTS distinction has absolutely nothing to do with the quality of the code.

Both of them are absolutely major releases that customers can adopt and enjoy and use with confidence.

However, the sort of even releases like 9.2 are not what we call long-term support releases.

So 9.1 was the first long-term support release.

9.3 should be another long-term support release.

And that has that sort of traditional multiple years of primary support and then several years of extended support before we would expect you to transition off.

Instead, with 9.2 and other releases, you typically get a full year of what we would call sort of primary support.

I forget the exact term for it, but it's

generally means we're going to apply bug fixes if there's any sort of problem with it.

We're going to do active development on that code line.

We're going to get you that release.

After that first year, what you might hear is, if you call into support on an issue about it, we're certainly going to work with you.

We're going to try and solve it.

If it's some major issue at our discretion, we'll still try and fix it.

But what you might hear is,

okay, the fix for that is really going to be a 9.3, and in order to consume that fix, we'd like you to go to that.

And I know that that's a major step for some customers.