Files
help365/platform/version-support-elma365-on-premises.html
koziavin 00717a92fb
All checks were successful
Deploy Static Site / deploy (push) Successful in 6m6s
update
2025-05-29 16:42:45 +04:00

227 lines
24 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE html>
<html lang="en">
<head>
<title>Versioning and LTS in BRIX On-Premises</title>
<meta name="generator" content="Help+Manual" />
<meta name="keywords" content="" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="This article provides a description of BRIXs policy regarding the provision of support for BRIX On-Premises." />
<meta name="picture" content="" />
<meta property="og:type" content="website" />
<meta property="og:title" content="Full documentation for BRIX365 platform. Low-code developer guide. User guide. Admin guide. Developer guide." />
<meta property="og:url" content="https://brix365.com/en/help" />
<meta property="og:image" content="" />
<link rel="icon" href="favicon.png" type="image/png" />
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet" />
<link rel="stylesheet" href="./jquery-ui.min.css" />
<link rel="stylesheet" href="default.css" />
<link rel="stylesheet" href="./search-yandex.css" />
<link rel="stylesheet" href="./article.css" />
<link rel="stylesheet" href="./glossary.css" />
<link rel="stylesheet" href="./theme.css" />
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="helpman_settings.js"></script>
<script type="text/javascript" src="helpman_topicinit.js"></script>
<script type="text/javascript" src="highlight.js"></script>
<script type="text/javascript">
$(document).ready(function(){highlight();});
</script>
</head>
<body>
<script>!function(e,t,c,n,r,a,m){e.ym=e.ym||function(){(e.ym.a=e.ym.a||[]).push(arguments)},e.ym.l=1*new Date;for(var s=0;s<document.scripts.length;s++)if(document.scripts[s].src===n)return;a=t.createElement(c),m=t.getElementsByTagName(c)[0],a.async=1,a.src=n,m.parentNode.insertBefore(a,m)}(window,document,"script","https://mc.yandex.ru/metrika/tag.js"),ym(83179930,"init",{clickmap:!0,trackLinks:!0,accurateTrackBounce:!0,webvisor:!0})</script><noscript><div><img alt=""src=https://mc.yandex.ru/watch/83179930 style=position:absolute;left:-9999px></div></noscript>
<header class="header elma-365">
<div class="container">
<a class="header__logo" href="https://brix365.com/en/help">
<img src="./logo-en.svg" alt="header logo">
</a>
<!-- <div class="hero__search-form" id="search-panel">
<form class="search-form" onsubmit="ym(83180416,'reachGoal','poisk')">
<label class="search-form__label">
<span id="reset-search" class="search__icon"></span>
<input class="search-form__input" type="text">
</label>
<input class="search-form__submit" type="submit" value="Submit">
</form>
</div> -->
<div class="hero__search-form" id="search-panel"> <form class="search-form"> <label class="search-form__label"> <span id="reset-search" class="search__icon"></span> <input class="search-form__input" type="text"> </label> <input class="search-form__submit" type="submit" value="Submit"> </form> </div>
<div class="hero__search">
<a href="#" id="search-icon" class="hero__search-icon">
<img src="search-icon-white.svg" alt="search string">
</a>
<a href="#" id="side-menu-icon" class="hero__side-icon">
<img src="side_menu.svg" alt="side menu">
</a>
</div>
<div class="header__navi">
<ul class="header__list"><li><span class="solution-select"><span class="solution-select__selected"></span><svg width="7" height="4" viewBox="0 0 7 4" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M1 1L3.5 3.5L6 1" stroke="white" stroke-linecap="round" stroke-linejoin="round"/></svg><ul class="solution-select__list"><li><a class="project-link" href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a class="project-link" href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a class="project-link" href="https://brix365.com/en/help/crm/crm_overview.html">CRM</a></li><li><a class="project-link" href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a class="project-link" href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li><li><a class="project-link" href="https://brix365.com/en/help/business_solutions/-elma365-store.html">Business Solutions</a></li></ul></span></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li><li><a href="https://tssdk.brix365.com/" target="_blank">SDK</a></li></ul>
</div>
</div>
</header>
<main class="main container">
<aside class="sidebar" id="sidebar">
<div class="sidebar__header">
<a class="header__logo" href="https://brix365.com/en/help">
<img src="./logo-light-en.svg">
</a>
<span class="sidebar__close elma-365-close" id="close"></span>
</div>
<div class="sidebar__wrapper" id="side-menu">
</div>
</aside>
<article class="article" id="article">
<div class="article-inner">
<div class="content">
<header class="article__header">
<div class="article__bread" style="display:flex; gap:10px;">
<span id="subcategory" class="search-res__item-category search-res__item-category_subcategory subcategory article__badge"></span>
<div class="topic__breadcrumbs">
<p>System architecture and requirements / Versioning and LTS in BRIX On-Premises</p>
</div>
</div>
<div class="topic__title"><h1 class="p_Heading1"><span class="f_Heading1">Versioning and LTS in BRIX On-Premises</span></h1>
</div>
</header>
<section class="article__content">
<div class="scroll-top-inner">
<a href="#h1-article" class="scroll-top"></a>
</div>
<!-- Placeholder for topic body. -->
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">This article provides a description of BRIXs policy regarding the provision of support for BRIX On-Premises.</p>
<p style="line-height: 1.20; margin: 7px 0 16px 0;"><a id="major" class="hmanchor"></a>Lets look at the main terms used in the article:</p>
<ul style="list-style-type:disc">
<li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Software Life Cycle</span> is the period of time from the moment of creation (release) to the moment of withdrawal from the process of support and operation.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Major Version</span> is a version of the system that contains significant differences from the previous similar release. Major releases of the BRIX On-Premises system can be subdivided into regular and Long Time Support (LTS) releases.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Long Time Support (LTS) release</span> is a stable version of the system that is updated according to the product life cycle. It is supported for a longer period of time than a regular major release.<br />
<a id="minor" class="hmanchor"></a>Please note, that the LTS release includes critical fixes that interfere with the normal functioning of the program and all security-related updates. Implementation of new functionality is included only in the development of major releases.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Minor Version</span> is a version of a system that contains minor differences within its main (major) release. A minor release includes changes related to increasing the stabilization of the software product. For example, bug fixes that do not change the functioning of the product.</li><li style="line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 16px;"><span style="font-weight: bold;">Release Support</span> is the correction of various bugs in the current version of a release.</li></ul>
<h2 class="p_Heading2"><span class="f_Heading2">BRIX product life cycle and version support </span></h2>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">The BRIX On-Premises software version numbering uses the <span style="font-weight: bold;">X.Y.Z</span> format, where: </p>
<ul style="list-style-type:disc">
<li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">X</span> is the year of the platform release: <span style="font-size: 13px; font-weight: bold; color: #394149;">2025</span><span style="font-size: 13px; color: #394149;">.1.0.</span></li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Y</span> is the serial number of the major version release in the year. Stats with a 1. It usually coincides with the month of the version release: <span style="font-size: 13px; color: #394149;">2025.</span><span style="font-size: 13px; font-weight: bold; color: #394149;">1</span><span style="font-size: 13px; color: #394149;">.0.</span></li><li style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;"><span style="font-weight: bold;">Z</span> is the sequence number of the minor version. It starts with a zero: <span style="font-size: 15px; color: #394149;">2025.1.</span><span style="font-size: 15px; font-weight: bold; color: #394149;">0</span><span style="font-size: 15px; color: #394149;">.</span></li></ul>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Support for a regular major release of version <span style="font-weight: bold;">X.Y</span> is performed from the release date and terminated when a release with version number <span style="font-weight: bold;">X.Y+2</span> is released, i.e. the current and previous major release is supported. For example, support for release <span style="font-size: 13px; color: #394149;">2024.7</span> will be terminated immediately after release 2024.9.</p>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">The LTS version release occurs in 2 phases:</p>
<ol style="list-style-type:decimal">
<li value="1" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">A major release of the product, <span style="font-weight: bold;">X.Y</span>, which is planned in the LTS, is released.</li><li value="2" style="text-align: justify; line-height: 1.20; margin-top: 7px; margin-right: 0; margin-bottom: 7px;">After the <span style="font-weight: bold;">X.Y+2</span> release, i.e. two months later, this release is marked (committed) as an LTS version as planned.</li></ol>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Support for the LTS version begins at the time of the commit and ends six months after the new LTS version is committed, i.e., after six major release cycles.</p>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Starting in April 2023, every sixth release will be considered an LTS release. However, it will be committed as LTS not at the time of release, but two months later, as this time is required for bug detection and fixing.</p>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Lets consider the LTS release support cycle as an example. Release 2024.10, released in November 2024, will be committed as an LTS release, i.e. in February 2025. The next LTS version is scheduled to be committed in August 2025, and version 2024.10 will be supported for six months after that. Thus version 2024.10 is planned to be supported for 15 months: from release in November 2024 to February 2026.</p>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Major releases are released every month.</p>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Minor releases are released when critical fixes appear.</p>
<p style="text-align: justify; line-height: 1.20; margin: 7px 0 16px 0;">Below is a diagram of the release life cycle. The arrows indicate the range of version support.</p>
<p class="p_Normal"><img alt="version-support-elma365-on-premises" title="version-support-elma365-on-premises" width="1072" height="524" style="margin:0;width:1072px;height:524px;border:none" src="version-support-elma365-on-premises.png"/></p>
<h2 class="p_Heading2"><span class="f_Heading2">Benefits of using Long Time Support releases </span></h2>
<p class="p_Normal">For stable and high-quality operation of the application, we recommend using the Long Time Support (LTS) release. It is necessary to update the software product to the latest minor version of this release, as it contains critical bug fixes. Also, using the LTS release for upgrading allows you to allocate resources in a more functional way for planning future updates. In this case, it is enough to wait for the announcement of a new LTS release and schedule the work to upgrade to the new version. At the same time, there is no need to update the system every time for a standard major release, the support time for which is significantly shorter. </p>
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Начало&nbsp;внимание</span></p>
<p class="p_Normal">BRIX reserves the right to change the timing of major releases and declare the release of a new release as a Long Time Support (LTS) release regardless of the time or order of release. </p>
<p class="p_CodeExample" style="page-break-inside: avoid;"><span class="f_CodeExample">Конец&nbsp;внимание</span></p>
<h2 class="p_Heading2"><a id="lts_schedule" class="hmanchor"></a><span class="f_Heading2">Release life cycle schedule</span></h2>
<p class="p_Normal">Support for the 2024.4 LTS release:</p>
<ul style="list-style-type:disc">
<li class="p_Normal">Release date: May 2024.</li><li class="p_Normal">LTS release commit: August 2024.</li><li class="p_Normal">Support is completely terminated after July 2025.</li></ul>
<p class="p_Normal">Support for the 2024.10 LTS release:</p>
<ul style="list-style-type:disc">
<li class="p_Normal">Release date: November 2024.</li><li class="p_Normal">LTS release commit: February 2025.</li><li class="p_Normal">Support is completely terminated after July 2025.</li></ul>
<p class="p_Normal">Support for the 2025.4 LTS release (this versions has not been released yet and is provided for illustration purposes):</p>
<ul style="list-style-type:disc">
<li class="p_Normal">Release date: May 2025.</li><li class="p_Normal">LTS release commit: August 2025.</li><li class="p_Normal">Support is completely terminated after July 2026.</li></ul>
<h2 class="p_Heading2"><span class="f_Heading2">Download a specific BRIX On-Premises version</span></h2>
<p class="p_Normal">You can install a specific BRIX On-Premises version, such as:</p>
<ul style="list-style-type:disc">
<li class="p_Normal">Latest major version.</li><li class="p_Normal">Minor versions of a specific release.</li><li class="p_Normal">Latest major LTS release.</li><li class="p_Normal">Minor version of a specific LTS release.</li><li class="p_Normal">Major version of a specific regular or LTS release. </li></ul>
<p class="p_Normal">All the download links are provided in <a href="links-for-install-elma365.html" class="topiclink">Links for downloading BRIX distribution packages</a>. </p>
<p class="p_Normal">To learn more about installing the system, see <a href="installing-elma365-enterprise.html" class="topiclink">Install BRIX Enterprise</a>, <a href="install-kubernetes-in-docker.html" class="topiclink">Install BRIX Standard</a>.</p>
<h2 class="p_Heading2"><span class="f_Heading2">Notification about termination of release support</span></h2>
<p class="p_Normal">Termination of release support means that for the respective system versions BRIX tech support will only consider requests containing platform-critical errors. Errors related to configuration issues and other types of requests will not be considered.</p>
<p class="p_Normal">In addition, updates and distributions of the specified versions will be unavailable, and documentation updates for these versions will be discontinued.</p>
<p class="p_Normal">For an up-to-date list of BRIX On-Premises release versions, please visit the tech support website. </p>
<p class="p_Normal">Read more about BRIX On-Premises update in the following articles: </p>
<ul style="list-style-type:disc">
<li class="p_Normal"><a href="version-update-enterprise.html" class="topiclink">Update version of BRIX Enterprise</a>.</li><li class="p_Normal"><a href="offline-version-update-enterprise.html" class="topiclink">Update version of BRIX Enterprise offline</a>.</li><li class="p_Normal"><a href="version-update-standard.html" class="topiclink">Update BRIX Standard</a>. </li></ul>
<div class="bottom-nav">
<a id="prev-link" class="topic__navi_prev" href="elma365-enterprise-on-premises.html">
<span class="bottom-nav__arrow bottom-nav__arrow--prev"></span> <span
class="bottom-nav__link">elma365-enterprise-on-premises.html</span>
</a>
<a id="next-link" class="topic__navi_next" href="saas-standard-limits.html">
<span class="bottom-nav__link">saas-standard-limits.html</span> <span
class="bottom-nav__arrow bottom-nav__arrow--next"></span>
</a>
</div>
<!-- добавляет на страницу строку блок Была ли статья полезной? -->
<div class="feedback" id="feedback"><div class="feedback-help"><span><b>Was this helpful?</b></span><form action="" method="POST" class="feedback-form" id="feedback-form"><div class="feedback__popup feedback__popup-response" id="feedback__popup_thx" style="display: none;">Thanks for your feedback!</div><div class="feedback__popup" id="feedback__popup_why" style="display: none;"><div class="feedback__popup-header">Please specify why:</div><input type="radio" name="category" id="bad_recommendation" value="bad_recommendation"><label for="bad_recommendation">Recommendations did not help me</label><input type="radio" name="category" id="difficult_text" value="difficult_text"><label for="difficult_text">Article is hard to understand</label><input type="radio" name="category" id="no_answer" value="no_answer"><label for="no_answer">Didn`t answer my question</label><input type="radio" name="category" id="bad_header" value="bad_header"><label for="bad_header">Content does not match the topic</label><input type="radio" name="category" id="other_reason" value="other_reason"><label for="other_reason">Other</label></div><div class="feedback__popup" id="feedback__popup-other" style="display: none;"><div class="feedback__popup-header">How we can improve it?</div><textarea class="feedback__textarea" name="other" id=""></textarea><input type="submit" class="feedback__other-btn" value="Submit"></div><div class="feedback-form__btn-group"><input type="radio" name="useful" id="feedback__useful_yes" value="true"><label for="feedback__useful_yes"><img src="like.svg" class="small-img" alt="like"><spanclass="feedback-form__btn-group_yes-btn">Yes</spanclass="feedback-form__btn-group_yes-btn"></label><input type="radio" name="useful" id="feedback__useful_no" value="false"><label for="feedback__useful_no"><img src="dislike.svg" class="small-img" alt="dislike"><spanclass="feedback-form__btn-group_no-btn">No</spanclass="feedback-form__btn-group_no-btn"></label></div><select name="category"><option disabled="">Please specify why</option><option value="bad_recommendation" selected="">Recommendations did not help me</option><option value="difficult_text">Article is hard to understand</option><option value="no_answer">Didn`t answer my question</option><option value="bad_header">Content does not match the topic</option><option value="other_reason">Other</option></select><input type="submit"></form></div><div class="found_typo"><p style="margin: 0px; margin-top: 16px !important;"><span><b>Found a typo?</b></span> Select it and press <i>Ctrl+Enter</i> to send us feedback</p></div></div>
</section>
</div>
<aside class="article__sidebar" style="display:none">
<input type="checkbox" />
<div class="article__arrow"></div>
<div class="table-of-contents elma365-right" id="toc2Content">
<h3 class="h3-toc">In this topic</h3>
<nav id="toc2"></nav>
</div>
</aside>
</div>
</article>
</main>
<footer class="footer">
<div class="footer-container">
<div class="footer-mobile">
<ul class="footer-mobile__list"><li><a href="https://brix365.com/en/" target="_blank">BRIX</a></li><li><a href="https://tssdk.brix365.com/en/latest/" target="_blank">SDK</a></li><li><a href="https://api.brix365.com/en/" target="_blank">API</a></li></ul><ul class="footer-mobile__list"><li><a href="https://brix365.com/en/help/platform/get-trial.html">Platform</a></li><li><a href="https://brix365.com/en/help/ecm/ecm-functions.html">ECM</a></li><li><a href="https://brix365.com/en/help/service/service-functions.html">Service</a></li><li><a href="https://brix365.com/en/help/projects/projects-functions.html">Projects</a></li></ul>
</div>
<div class="footer-wrap">
<div><span class="mobile-question-popup">Send feedback</span><form method="POST" action class="question__popup question-xs" id="question__popup"><div class="question-wrap"><span class="close"></span><span class="title">Ask a question</span><label for="help_question" style="display: none;"></label><textarea name="help_question" id="help_question"></textarea><input type="submit" value="Send"></div></form><div class="hidden fade-in question-success-xs">Sent</div></div>
<div class="footer-flex-b">
<span class="footer-copy">&copy; 2025 BRIX</span>
<ul class="footer-list">
<li class="footer-item">
<a href="#" class="arrow-top" style="display: block;"></a>
</li>
</ul>
</div>
</div>
</div>
</footer>
<iframe name="hmnavigation" style="display:none!important"></iframe>
<script src="./jquery-ui.js"></script>
<!--script src="//cdn.jsdelivr.net/npm/featherlight@1.7.14/release/featherlight.min.js" type="text/javascript" charset="utf-8"></script-->
<script src="./jquery.tocify.min.js"></script>
<script src="./TypoReporter.min.js"></script>
<script src="./google-search.js"></script>
<script src="./main.js"></script>
</body>
</html>