[Topfi]

Appears the only difference to 3.0 Pro Preview is Medium reasoning. Model naming has long gone from even trying to make sense, but considering 3.0 is still in preview itself, increasing the number for such a minor change is not a move in the right direction.

[GrayShade]

Maybe that's the only API-visible change, saying nothing about the actual capabilities of the model?

[xnx]

> increasing the number for such a minor change is not a move in the right direction

A .1 model number increase seems reasonable for more than doubling ARC-AGI 2 score and increasing so many other benchmarks.

What would you have named it?

[Topfi]

My issue is that we haven't even gotten the release version of 3.0, that is also still in Preview, so may stick with 3.0 till that has been deemed stable.

Basically, what does the word "Preview" mean, if newer releases happen before a Preview model is stable? In prior Google models, Preview meant that there'd still be updates and improvements to said model prior to full deployment, something we saw with 2.5. Now, there is no meaning or reason for this designation to exist if they forgo a 3.0 still in Preview for model improvements.

[argsnd]

I disagree. Incrementing the minor number makes so much more sense than “gemini-3-pro-preview-1902” or something.

[jannyfer]

According to the blog post, it should be also great at drawing pelicans riding a bicycle.