Dave Rosenthal

That was more the angle I was coming from. When the train leaves the station once a year, you better get your stuff on it, whether it's ready or not. And I appreciate, I didn't know the history of where it came from. So I think this is definitely progress and improvement and predictability. You know, each time of year it's going to go out, et cetera, et cetera.

And it makes a lot of sense, especially a large project like this with tons of people using it. you want to be predictable, but also not too frequent. I would probably tend towards more frequent because now you have the train leaving the station more times. And if you don't, if you miss this one, that's all right. We got another train leaving six weeks from now.

And it makes a lot of sense, especially a large project like this with tons of people using it. you want to be predictable, but also not too frequent. I would probably tend towards more frequent because now you have the train leaving the station more times. And if you don't, if you miss this one, that's all right. We got another train leaving six weeks from now.

And so you can hop on when it's ready versus having to hop on once a year. And that's, you know, we've seen success in projects like Chrome, et cetera, with like rolling every six weeks, whatever's ready, we're going to ship a new version. I don't know if that works with languages and runtimes. You guys know way better than I do, which is why I asked the question.

And so you can hop on when it's ready versus having to hop on once a year. And that's, you know, we've seen success in projects like Chrome, et cetera, with like rolling every six weeks, whatever's ready, we're going to ship a new version. I don't know if that works with languages and runtimes. You guys know way better than I do, which is why I asked the question.

Why don't we make up another term for it?

Why don't we make up another term for it?

Ha ha!

Ha ha!

Okay.

Okay.

Yeah. Recursive acronyms I'm well aware of, but I'm not a Monty Python guy, so I missed completely this reference.

Yeah. Recursive acronyms I'm well aware of, but I'm not a Monty Python guy, so I missed completely this reference.

Like I have to watch it. Is it from Holy Grail or which movie is this?

Like I have to watch it. Is it from Holy Grail or which movie is this?

A little obscure reference to build an entire Python ecosystem around, but okay.

A little obscure reference to build an entire Python ecosystem around, but okay.

Again, this background is spectacular because you do run out of references with snakes. How many things can you actually reference? But with Monty Python, there's just countless references you can make, just people won't get them.

Again, this background is spectacular because you do run out of references with snakes. How many things can you actually reference? But with Monty Python, there's just countless references you can make, just people won't get them.

Good stuff. Okay, good meta conversation on release cadence. I think I agree with all your points. You have to find that sweet spot and as frequent as you can be reliable without being too frequent. And that probably varies per project. And I'm happy that you guys are happy with once a year. Certainly better than what y'all were doing before. That's very cool.