blob: 7538fa72deec7498186f148b0c42122b9ae41ebf [file] [log] [blame] [edit]
<!--#include file="header.html" -->
<link href="css/lts.css" rel="stylesheet">
<header class="br-lts-header">
<div class="br-lts-header-bg"></div>
<div class="br-lts-header-content">
<div class="br-lts-header-title">
Buildroot LTS
</div>
<div class="br-lts-header-title">
3-year long-term support with security fixes
</div>
</div>
</header>
<main class="br-lts-main">
<a href="#objectives" id="objectives" class="br-lts-section-header">
<div class="br-lts-bg-grid"></div>
<div class="br-lts-title-box">LTS Objectives</div>
<div class="br-lts-decoration-dot"></div>
</a>
<div class="br-lts-item-row">
<div class="br-lts-item-number">1</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
3-year LTS support
</h2>
<p class="br-lts-item-text">
Starting with version <code>2025.02</code> the LTS support has been extended to
<strong>3 years</strong>, replacing the previous 1-year cycle.
</p>
</div>
</div>
<div class="br-lts-separator"></div>
<div class="br-lts-item-row">
<div class="br-lts-item-number">2</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Vulnerability tracking & reporting
</h2>
<p class="br-lts-item-text">
Tracking of the vulnerabilities affecting Buildroot
is available at
<a href="https://security.buildroot.org/2025.02.x/vulnerability">security.buildroot.org</a>.
<br/>
LTS stewards ensure this data remains up-to-date by actively
maintaining Buildroot packages metadata.
</p>
</div>
</div>
<div class="br-lts-separator"></div>
<div class="br-lts-item-row">
<div class="br-lts-item-number">3</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Sponsored LTS stewards
</h2>
<p class="br-lts-item-text">
To ensure a consistent release cadence and maintenance
workflow, paid LTS stewards are assigned to the weekly LTS
maintainance tasks.
</p>
</div>
</div>
<div class="br-lts-separator"></div>
<div class="br-lts-item-row">
<div class="br-lts-item-number">4</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Dedicated backports
</h2>
<p class="br-lts-item-text">
Vulnerability fixes applied to the <code>master</code> branch will be
prioritized for backporting to the LTS & stable branches.
</p>
</div>
</div>
<a href="#releases" id="releases" class="br-lts-section-header">
<div class="br-lts-bg-grid"></div>
<div class="br-lts-title-box">Releases</div>
<div class="br-lts-decoration-dot"></div>
</a>
<p>
The Buildroot LTS sponsorship initiative has evolved from a more
comprehensive understanding of the needs of our user base.
<br/>
To address these requirements the release model evolves into the following.
<br/>
The LTS releases are now extended for a 3-year period. An LTS release
is started every 2 years.
In between, stable releases are made every 3 months.
</p>
<br/>
<div class="br-lts-chart">
<div class="br-lts-chart-head">
<div class="br-lts-head-spacer"></div>
<div class="br-lts-chart-head-label br-lts-span-year">2025</div>
<div class="br-lts-chart-head-label br-lts-span-year">2026</div>
<div class="br-lts-chart-head-label br-lts-span-year">2027</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2025.02</div>
<div class="br-lts-bar br-lts-bar--long br-lts-col-start-2">3 Years Support (LTS)</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2025.05</div>
<div class="br-lts-bar br-lts-col-start-3">3 mo</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2025.08</div>
<div class="br-lts-bar br-lts-col-start-4">3 mo</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2025.11</div>
<div class="br-lts-bar br-lts-col-start-5">3 mo</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2026.02</div>
<div class="br-lts-bar br-lts-col-start-6">3 mo</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2026.05</div>
<div class="br-lts-bar br-lts-col-start-7">3 mo</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2026.08</div>
<div class="br-lts-bar br-lts-col-start-8">3 mo</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2026.11</div>
<div class="br-lts-bar br-lts-col-start-9">3 mo</div>
</div>
<div class="br-lts-chart-row">
<div class="br-lts-chart-label">2027.02</div>
<div class="br-lts-bar br-lts-bar--long br-lts-col-start-10">3 Years Support (LTS)</div>
</div>
<div class="br-lts-chart-row br-lts-chart-row--faded">
<div class="br-lts-chart-label">...</div>
</div>
</div>
<br/>
<br/>
<p>
More details about the LTS workflow at <a href="https://gitlab.com/buildroot.org/buildroot-lts-tools">buildroot.org/buildroot-lts-tools</a>.
</p>
<a href="#organization" id="organization" class="br-lts-section-header">
<div class="br-lts-bg-grid"></div>
<div class="br-lts-title-box">How we work</div>
<div class="br-lts-decoration-dot"></div>
</a>
<p>
Each week the LTS stewards defines the set of commits to
analyze based on the previous week commits to the master branch. The
commits are then annotated to define a list of candidates for the LTS
branches.
<br><br>
On Thursday the candidates are cherry-picked to a staging branch to be
reviewed by the other maintainers. On Thursday evening the branch is
synced with upstream and contributors are notified. Feedback from
users, sponsors and autobuilders are then collected and vulnerability
analyses updated.
</p>
<br/>
<div class="br-lts-chart">
<div class="br-lts-chart-head">
<div class="br-lts-head-spacer"></div>
<div class="br-lts-chart-head-label br-lts-span-day">Monday</div>
<div class="br-lts-chart-head-label br-lts-span-day">Tuesday</div>
<div class="br-lts-chart-head-label br-lts-span-day">Wednesday</div>
<div class="br-lts-chart-head-label br-lts-span-day">Thursday</div>
<div class="br-lts-chart-head-label br-lts-span-day">Friday</div>
<div class="br-lts-chart-head-label br-lts-span-day">...</div>
</div>
<div class="br-lts-chart-row br-lts-chart-row--tall">
<div class="br-lts-chart-label">Freeze weekly commit set from master</div>
<div class="br-lts-bar br-lts-col-start-2"></div>
</div>
<div class="br-lts-chart-row br-lts-chart-row--tall">
<div class="br-lts-chart-label">Apply branch specific patches</div>
<div class="br-lts-bar br-lts-col-start-2"></div>
</div>
<div class="br-lts-chart-row br-lts-chart-row--tall">
<div class="br-lts-chart-label">Analysis & commit annotation</div>
<div class="br-lts-bar br-lts-bar--span-6 br-lts-col-start-2"></div>
</div>
<div class="br-lts-chart-row br-lts-chart-row--tall">
<div class="br-lts-chart-label">Cherry picking to staging branch</div>
<div class="br-lts-bar br-lts-bar--span-2 br-lts-col-start-7"></div>
</div>
<div class="br-lts-chart-row br-lts-chart-row--tall">
<div class="br-lts-chart-label">Sync with upstream branch</div>
<div class="br-lts-bar br-lts-col-start-9"></div>
</div>
<div class="br-lts-chart-row br-lts-chart-row--tall">
<div class="br-lts-chart-label">Update vulns</div>
<div class="br-lts-bar br-lts-col-start-10"></div>
</div>
</div>
<a href="#benefits" id="benefits" class="br-lts-section-header">
<div class="br-lts-bg-grid"></div>
<div class="br-lts-title-box">Sponsorship benefits</div>
<div class="br-lts-decoration-dot"></div>
</a>
<div class="br-lts-item-row">
<div class="br-lts-item-number">1</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Long-term sustainability
</h2>
<p class="br-lts-item-text">
Sponsors ensure the long-term sustainability of the Buildroot
LTS effort with dedicated stewards assigned to tasks such as
backporting, security monitoring and LTS releases.
</p>
</div>
</div>
<div class="br-lts-separator"></div>
<div class="br-lts-item-row">
<div class="br-lts-item-number">2</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Recognition of your sponsorship
</h2>
<p class="br-lts-item-text">
Sponsors can be publicly acknowledged on the Buildroot website.
Sponsors may provide a logo linking to a webpage of their
choice.
</p>
</div>
</div>
<div class="br-lts-separator"></div>
<div class="br-lts-item-row">
<div class="br-lts-item-number">3</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Direct interaction with LTS stewards
</h2>
<p class="br-lts-item-text">
Sponsors may submit queries and requests regarding
Buildroot LTS and security updates.
</p>
</div>
</div>
<div class="br-lts-separator"></div>
<div class="br-lts-item-row">
<div class="br-lts-item-number">4</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Assignment of priorities for package tracking
</h2>
<p class="br-lts-item-text">
Buildroot integrates more than 2000 open source packages,
many of which do not offer long-term stable releases or
security updates.
<br/>
<br/>
Sponsors may submit a priority list indicating: <br/>
- Packages of interest<br/>
- Architectures of interest<br/>
</p>
</div>
</div>
<div class="br-lts-separator"></div>
<div class="br-lts-item-row">
<div class="br-lts-item-number">5</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Testing of your packages
</h2>
<p class="br-lts-item-text">
To make sure the packages of interest to the sponsors don't
include regressions between releases.
Sponsors may submit a list of packages to be tested
before an LTS & stable release.
</p>
</div>
</div>
<div class="br-lts-separator"></div>
<div class="br-lts-item-row">
<div class="br-lts-item-number">6</div>
<div class="br-lts-item-content">
<h2 class="br-lts-item-title">
Personalized security reports
</h2>
<p class="br-lts-item-text">
Sponsors receive personalized security reports for their
Buildroot packages in the form of
<a href="https://security.buildroot.org/">security.buildroot.org</a>
with comparison with the upstream branches.
</p>
</div>
</div>
<a href="#sponsor" id="sponsor" class="br-lts-section-header">
<div class="br-lts-bg-grid"></div>
<div class="br-lts-title-box">Sponsor now !</div>
<div class="br-lts-decoration-dot"></div>
</a>
<p>
Interested ? Contact us at
<a href="mailto:buildroot-lts@buildroot.org">buildroot-lts@buildroot.org</a>
to learn more about the different sponsorship tiers and get all the
details about the sponsorship.
</p>
</main>
<!--#include file="footer.html" -->