Issue 13 · Nov 2–8, 2026Editions · Glossary · Archive · Method · RSS · HU / ENG

News of the AI era, curated weekly

Glossary › Developer basics

expenditure

in English: release

basicwidespread

A release is a finalized, version-numbered state of a software or AI model that the creators officially hand over to users.

In plain terms

Software is never fully finished: developers improve and expand it day by day. A release is the moment when they say: this state is good enough now, we will give it to people. It gets a version number, and from then on it can be referenced precisely.

It is like book publishing. The author could polish the manuscript indefinitely, but eventually it must be sent to the printer. What goes on sale is the first edition; errors are corrected later in a revised second edition. The copy on your shelf does not change as a result. With software it is partly different: a program installed on your machine changes only when updated (often automatically), while online services are replaced by their creator on its own servers, so there is nothing for you to do.

The same logic applies in the AI world. A language model, a chat application, or a coding agent is released in versions, which is why the same tool might behave slightly differently from one week to the next.

The release is therefore not the work itself, but its fixed, numbered snapshot. This makes it possible to track what has changed and to revert to a previous, working state in case of issues.

How it works

  1. Developers gather completed new features and bug fixes, then decide what goes into the next release and what is deferred.
  2. The selected state is tested: first with automated checks, then often in a narrower scope, as a preliminary (beta or release candidate) version.
  3. The state receives a version number, for example 2.4.1. The numbers usually indicate the scale of the change: a major overhaul, a new feature, or just a bug fix.
  4. The release notes are prepared, listing what is new, what has improved, and what functions differently compared to the previous version.
  5. The release is published: it goes into the app store, onto the download page, or onto the service's servers. Often gradually, first to only a small portion of users.

An everyday example

In the morning, your phone notifies you that your banking app has been updated, and you see this in the description: "version 3.12: faster login, bug fixes." This is a new release. The same happens when you read in the news that a company has released a new version of its language model.

Who is affected

everyonePrograms running on your phone, computer, and car are updated in releases, so what your device can do and how secure it is depends on these.
developerThe release sets the rhythm of your work: it defines deadlines, testing gates, and responsibility for what reaches users. → Code
entrepreneur, executiveIf your company relies on a software or AI model, a new release can change your processes, costs, and the quality of results.
employeeAfter new releases of workplace software, familiar menus or functions may change, so it is worth reviewing what has been updated. → Work & HR

A common misconception

MythThe new version is always better, so it must be installed immediately.
In realityA new release may introduce new bugs and remove familiar features. Security patches should be applied quickly, but with major overhauls, many companies intentionally wait and test first.

Limits and risks

Similar, but not the same

Related concepts

Broader

software development, software lifecycle

Narrower

beta version, release candidate, bug-fix release, long-term support release

On the edge

version control, installation, update, release notes, continuous delivery

A brief history

The software release practice originates from the mainframe era: manufacturers already delivered programs in numbered releases on magnetic tape in the 1960s. Later, new versions of boxed programs reached stores on discs. The principle of "release early and often" was made widely known by Eric S. Raymond's 1997 essay, The Cathedral and the Bazaar; today, many services release new versions several times a day.

Where things stand

At the end of 2026, a release is a basic concept in the software industry, and most of the process is automated. Because AI models and agents are released in rapid succession, you also come across the term regularly in everyday news.

Status: 2026 November

In the news

Appears in 132 Agent Age stories; the curve shows weekly occurrence in the news magazine.

Also known as

expenditure · release · software release · version release · Appearance · software release

Sources

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.