Hacker News new | ask | show | jobs
by alwillis 262 days ago
It's pretty common to refer to models by the month and year they were released.

For example, the latest Gemini 2.5 Flash is known as "google/gemini-2.5-flash-preview-09-2025" [1].

[1]: https://openrouter.ai/google/gemini-2.5-flash-preview-09-202...

5 comments

If they're going to include the month and year as part of the version number, they should at least use big endian dates like gemini-2.5-flash-preview-2025-09 instead of 09-2025.
Or, you know, just Gemini 2.6 Flash. I don't recall the 2.5 version having a date associated with it when it came out, though maybe they are using dates now. In marketing, at least, it's always known as Gemini 2.5 Flash/Pro.
It had a date, but I also agree this is extremely confusing. Even semver 2.5.1 would be clearer IMO.
It always had dates... They release multiple versions and update regularly. Not sure if this is the first 2.5 Flash update, but pretty sure Pro had a few updates as well...

This is also the case with OpenAI and their models. Pretty standard I guess.

They don't change the versioning, because I guess they don't consider it to be "a new model trained from scratch".

>For example, the latest Gemini 2.5 Flash is known as "google/gemini-2.5-flash-preview-09-2025" [1].

That "example" is the name used in the article under discussion. There's no need to link to openrouter.ai to find the name.

I'm pretty sure Google just does that for preview models and they drop the date from the name when it's released.
If only there was some of versioning nomenclature they could use. Maybe even one that is … semantic? Oh how I wish someone would introduce something like this to the software engineering field. /s

In all seriousness though, their version system is awful.