QGIS does not release software the way most applications do, on a vague whenever-it-is-ready rhythm. It runs on a published calendar: a new release every four months, a feature freeze before each one, and a long term release line that trades novelty for a year or more of quiet, bug-fix-only maintenance. Most users meet this system as a version number in a download list and never learn the rules underneath it, which is a shame, because the rules are the useful part. Once you can read the QGIS Road Map, you can answer questions that otherwise become superstition: when the next LTR lands, how long your current one stays maintained, why a point release never surprises you with a new tool, and when to schedule an upgrade so it lands in a calm month instead of a deadline week. This guide teaches the calendar as a system. The separate question of whether you personally should install the LTR or the latest release is a decision our comparison article owns, and it is handed off below; here, the machinery comes first.
Home / GIS and Open Map Data for Beginners
QGIS Long Term Release (LTR): The Release Calendar, Point Releases, and How to Plan Around Them

Photo: Nemuel Sereti / Pexels
Ride the Calendar: The LTR Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
The Four-Month Rhythm and the Road Map Table
The QGIS Road Map page at qgis.org is the primary source and the spine of the whole system. Its schedule table lists each release with its planned dates, and the pattern in it is simple once seen: a new feature release every four months, three per year, each developed in the open with a feature freeze in the run-up to release day. The freeze is the discipline that makes the calendar possible: past the freeze date, developers stop adding features to the coming release and only fix what is broken, so the release that ships is the release that was planned. Every third release is designated a Long Term Release, a pattern that has held since 2.8, the first LTR. Because the cycle is arithmetic, the road map can be read forward: find the current LTR in the table, count two releases ahead, and the third is the next LTR, with its month already printed. At the time this guide was researched, the download page stood at LTR 3.44.15 and Latest 4.2.3, and the road map table slated 4.4.0 as the next LTR. Those numbers will age; the rhythm that produced them will not, and the rhythm is what you are learning to read.
What an LTR Actually Is
An LTR is not a different program and not a cut-down edition. It is one of the regular four-month releases, chosen by its position in the cycle, that the project then maintains until the next LTR occurs. Maintenance has a precise meaning here: the LTR branch continues to receive bug fixes, delivered as monthly point releases, while new features go only into the regular release line. So 3.44.0 the day it shipped and 3.44.15 a year later are the same feature set at two levels of polish: the second number stays fixed for the life of the line, and the third number counts the maintenance releases it has received. Nothing about the designation is retroactive or honorary; an LTR is simply the release standing in the LTR slot of the calendar, and when the next LTR arrives, the slot, and the maintenance effort, moves to it. Understanding that the title is positional rather than qualitative dissolves most LTR mythology: the LTR is not the release the developers trust most in the abstract, it is the release the calendar guarantees to keep fixing.

Point Releases: Bug Fixes Only, on a Monthly Beat
The point release is the LTR's maintenance made visible, and its defining rule deserves emphasis: point releases carry bug fixes only, and no new features. That single rule is what makes an LTR safe to run in production. An administrator who installs 3.44.7 over 3.44.3 is not re-testing workflows, re-training staff, or wondering whether a dialog moved; the tools behave as they did, minus the defects that were found and fixed. The monthly cadence matters for planning: an organization can schedule a standing maintenance window, apply the month's point release, and know in advance that the update's character never changes. The same monthly rhythm also tells you how to read a bug report against the calendar: a defect fixed in the development line reaches LTR users through the backport process into a coming point release, not instantly, and the point release notes for each month are the record of what actually arrived. Patience is built into the design; the LTR trades immediacy for the guarantee that nothing new can break.
How an LTR Enters and Leaves Maintenance
The lifecycle has four beats, all readable from the road map. First, a regular release ships in its four-month slot. Second, because it stands third in its cycle, it is designated the LTR, and from that moment the project's maintenance effort centers on it. Third, it accumulates monthly point releases while two further feature releases ship beside it in the regular line; during this overlap the LTR is maintained and the newer line is where features land. Fourth, the next LTR ships, maintenance moves to it, and the old LTR's point releases stop: the line is finished, not broken, and it will keep running exactly as its last point release left it, forever. That fourth beat is the one to plan around, because it is a date you can know a year in advance. An organization that checks the road map when it adopts an LTR can write the successor's arrival month into its own calendar the same day, and budget the migration as a scheduled event rather than discovering, mid-project, that its platform aged out of maintenance.
Planning Upgrades Around the Calendar
With the machinery in view, planning becomes arithmetic. Adopt near the start of an LTR's life if you want the longest maintenance runway from a single install. Expect two feature releases to pass you by during that life, and read their release notes as a preview of your next platform rather than as temptations. Schedule the migration for the weeks after the next LTR's first point releases, when the new line has absorbed its earliest fixes, rather than on the LTR's launch day itself. And treat point releases as routine hygiene, applied monthly without ceremony, precisely because the bug-fixes-only rule makes them boring. The calendar also settles team questions: a mixed team standardizes on the LTR line and a named point release, so a project file passed between machines meets the same behavior everywhere, and the road map gives the team a shared, public answer to when that standard will next change. Which line belongs on your machine in the first place, the LTR or the latest release, depends on plugins, projects, and appetite for new features; that decision is worked through in full in the comparison linked below, and this guide deliberately leaves it there.
Reading the Road Map Like a Professional
Three habits separate reading the road map from glancing at it. First, read the table, not the headlines: blog posts celebrate feature releases, but the table is where freeze dates, release dates, and the LTR succession are printed as commitments. Second, note the freeze date of the release you are waiting for, because after freeze, the feature set is final and documentation, tutorials, and plugin updates start converging on it; a feature absent at freeze is absent until the next cycle. Third, check the road map before any long project starts, the way you would check a tide table: a six-month project begun two months before an LTR transition can either ride the old line to its end or deliberately start on the new one, and either choice is fine when it is a choice. The road map is one page, maintained by the project itself, and it converts QGIS's release policy from folklore into a schedule you can plan a year of work against. That is the entire value of the LTR system, and it is available to anyone willing to read one table.
What the Freeze Protects, and What It Costs
The feature freeze deserves its own moment, because it is the least visible part of the calendar and the part that makes the rest trustworthy. In the weeks before a release, the codebase stops accepting new features entirely: the release branch is cut, and only bug fixes land on it. For users, the freeze is why a QGIS release is a known quantity on day one rather than a moving target; the feature list printed in the visual changelog is final, the documentation writers and tutorial authors can work against a fixed program, and plugin developers get a stable surface to update against. For the LTR line, the freeze matters twice: the release that becomes an LTR was itself frozen and hardened before designation, and its point releases then inherit the same conservatism for the whole of its maintained life. The cost is real and worth naming: a feature finished the week after a freeze waits a full cycle for the next release, and an LTR user waits longer still, watching two feature releases pass with tools they cannot have yet. That is not a defect in the system; it is the system. The calendar sells predictability, and the freeze is where the predictability is manufactured. Users who find the wait intolerable are exactly the users the latest-release line exists for, which is why the project maintains both lines from one codebase rather than forcing a single temperament on everyone.
A Note on Names and Numbers
Two naming confusions are worth dissolving before you go. First, the version number is the calendar written small: in 3.44.15, the 3.44 names the release line, the slot in the cycle that became this LTR, and the 15 counts the maintenance releases the line has received, so the number itself tells a reader which line you run and how seasoned it is. Second, older hands may remember the phrase long term release spelled against a predecessor scheme from the 2.x era; the modern system is the one this guide describes, one codebase, two lines, LTR and Latest, differing in maintenance policy rather than in kind. When a tutorial, a plugin page, or a colleague's advice names a version, translate it through the calendar first: which line, which point release, how far from the next succession. Advice that ignores those three facts is folklore, however confident it sounds.
Related Guides
If this page answered part of the question, these GIS guides cover the rest of the same ground:
- QGIS LTR vs Latest: Which Line Belongs on Your Machine: The install decision this guide deliberately hands off: plugins, projects, teams, and the safe upgrade procedure.
- QGIS Browser Panel: The Front Door to Your Data: The panel every QGIS workflow starts from, taught as a system.
- QGIS Processing Toolbox: Run, Batch, Model, Repeat: The framework whose behavior stays stable across an LTR's point releases.
- QGIS Keyboard Shortcuts: The Defaults by Task, and How to Rebind Them: The fluency layer that survives every upgrade unchanged.
Frequently Asked Questions
How often does QGIS release a new version?
On a fixed calendar: a new feature release every four months, three per year, each preceded by a feature freeze during which only fixes are accepted. The QGIS Road Map page at qgis.org publishes the schedule table with the dates.
What makes a release an LTR?
Position in the cycle. Every third release, a pattern held since 2.8, is designated the Long Term Release and is then maintained with bug fixes until the next LTR takes over. It is the same program as the regular release that shipped in that slot, kept polished instead of superseded.
Do LTR point releases add new features?
No. Point releases carry bug fixes only, delivered on a roughly monthly cadence. That rule is the point of the LTR: the feature set you installed is the feature set you keep, with defects removed over time.
How long is an LTR maintained?
Until the next LTR occurs: through the two feature releases that follow it in the four-month cycle, which works out to roughly a year of monthly point releases. The exact succession dates are printed in the road map schedule table.
Where do I check which LTR comes next?
The QGIS Road Map page. Find the current LTR in the schedule table, count two releases forward, and the third is the next LTR with its planned month. At the time of research the binaries stood at LTR 3.44.15 and Latest 4.2.3, with 4.4.0 slated as the next LTR.
Photo credits: Nemuel Sereti (Pexels); Nemuel Sereti (Pexels). Photos are served from this site; follow the credit to the library page for the original.