NodeBB/nodebb.org
2
0
Fork 0
mirror of https://hk.gh-proxy.com/https://github.com/NodeBB/nodebb.org.git synced 2025-10-03 08:43:39 +08:00
Code Issues Projects Packages Wiki Activity Actions

one more

Browse source
This commit is contained in:
Barış Soner Uşaklı 2025-04-13 19:20:18 -04:00
parent ad6cb8bcf4
commit 2783a3b04a
4 changed files with 187 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

164
blog/changes-to-our-release-branches.html Normal file
View file

@ -0,0 +1,164 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Changes to our release branches - NodeBB - Modern Community Forum Software</title>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="description" content="Blog of NodeBB Forum Software - The Modern Discussion Platform">
<meta name="author" content="NodeBB Inc.">
<meta name="keywords" content="nodebb, node.js, forum, discussion, community, software, hosting, blog">

<link rel="apple-touch-icon" sizes="180x180" href="/images/icons/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/images/icons/32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/images/icons/16x16.png">
<link rel="shortcut icon" href="/images/icons/favicon.ico">

<!-- Google Fonts: Inter & Poppins -->
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;600&family=Poppins:wght@400;600&display=swap" rel="stylesheet">

<!-- Bootstrap 5 CSS -->
<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/css/bootstrap.min.css" rel="stylesheet" crossorigin="anonymous">

<!-- Font Awesome -->
<link href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.0/css/all.min.css" rel="stylesheet" crossorigin="anonymous" referrerpolicy="no-referrer" />

<!-- our css-->
<link href="/css/style.css" rel="stylesheet">

<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-V0P62EB8Q6"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());

gtag('config', 'G-V0P62EB8Q6');
</script>
</head>
<body class="p-0 py-5 p-lg-5">
<!-- Navbar -->
<nav class="navbar navbar-expand-lg bg-body fixed-top shadow-sm">
<div class="container-lg">
<a class="navbar-brand py-2" href="/">
<img src="/images/brand/nodebb-logo.svg" style="height: 36px; width: auto;" alt="NodeBB Logo" />
</a>
<button class="navbar-toggler border-0" type="button" data-bs-toggle="collapse" data-bs-target="#navbarMenu" aria-controls="navbarMenu" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse justify-content-end" id="navbarMenu">
<ul class="nav nav-underline gap-4 flex-column flex-lg-row align-items-end align-items-lg-center mt-4 mt-lg-0">
<li class="nav-item">
<a href="/" class="nav-link active text-reset fw-semibold">HOME</a>
</li>
<li class="nav-item">
<a href="/product" class="nav-link text-reset fw-semibold">PRODUCT</a>
</li>
<li class="nav-item">
<a href="/pricing" class="nav-link text-reset fw-semibold">PRICING</a>
</li>
<li class="nav-item">
<a href="/services" class="nav-link text-reset fw-semibold">SERVICES</a>
</li>
<li class="nav-item dropdown">
<a href="#" target="_blank" role="button" data-bs-toggle="dropdown" aria-expanded="false" class="nav-link dropdown-toggle text-reset fw-semibold">RESOURCES</a>
<ul class="dropdown-menu dropdown-menu-end border-0 shadow p-1">
<li><a href="https://community.nodebb.org/" class="dropdown-item rounded-1" target="_blank">Community</a></li>
<li><a href="https://try.nodebb.org/" class="dropdown-item rounded-1" target="_blank">Demo Site</a></li>
<li><a href="https://community.nodebb.org/category/28/answers" class="dropdown-item rounded-1" target="_blank">Answers</a></li>
<li><a href="https://docs.nodebb.org/" class="dropdown-item rounded-1" target="_blank">Documentation</a></li>
<li><a href="/bounty" class="dropdown-item rounded-1">Bug Bounty</a></li>
</ul>
</li>
<li class="nav-item">
<a href="/contact" class="btn btn-warning rounded-pill">Contact Us</a>
</li>
<li class="nav-item">
<a href="https://manage.nodebb.org/register" class="btn btn-primary"><i class="fa-solid fa-rocket"></i> Start Free Trial</a>
</li>
</ul>
</div>
</div>
</nav>

<!-- Page Content -->
<div class="container-lg mt-5">
<!-- Home -->
<div id="home-tab-pane">
<div class="row pt-2 pt-lg-5">
<div class="col-12 d-flex flex-column gap-4">
<h1 class="display-1 fw-bold fs-1">
Changes to our release branches
</h1>
</div>
</div>

<!-- blog post -->
<div class="py-5">
<div class="d-flex gap-2 align-items-center mb-4">
<a href="https://community.nodebb.org/user/julian"><img class="rounded-circle" width="32" src="https://community.nodebb.org/assets/uploads/profile/uid-2/2-profileavatar-1738544541106.jpeg"></a> <a href="https://community.nodebb.org/user/julian" class="fw-semibold">Julian Lam</a> <span class="text-secondary">7/26/2022, 2:18:20 PM</span>
</div>
<div class="">
<h2>What is a release branch?</h2><p>Whenever we make a NodeBB release, whether it be a patch release, minor release, or a major release, we also push the code to specific <strong>release branches</strong>, for those who wish to subscribe to a specific set of releases.</p><p>For example, an administrator who currently runs v1.18.0 of NodeBB might not want to pull the latest code and upgrade all the way to v2.2.5 (as of this writing). They may want to upgrade to the latest version on the v1.18.x release branch, which is v1.18.6. By tracking the release branch, they are safe from accidentally upgrading to a potentially breaking version of NodeBB.</p><h2>Why the change?</h2><p><a href="https://nodebb.org/blog/plugin-compatibility-semver/">Up until recently, we released new versions when we felt it was safe to do so</a>. A patch version could contain new functionality <em>in addition to bug fixes</em>, and minor versions contained breaking changes. A major version bump denoted a radical change (e.g. <a href="https://nodebb.org/blog/migration-guide-for-v2/">the switch to webpack</a>.)</p><p>However, lumping in enhancements and bug fixes meant that occasionally, regressions and unexpected behaviour could occur during upgrades.</p><p>Since the dawn of version 2.0, we wanted to accelerate our release schedule, and remove any roadblocks to a patch release. More information is provided in the <a href="https://nodebb.org/blog/plugin-compatibility-semver/">semver blog post</a>, but in short:</p><ul><li>Patch versions contain bug fixes only</li><li>Minor versions contain bug fixes <em>and enhancements</em></li><li>Major versions contain breaking changes</li></ul><h2>What's the change?</h2><p>Instead of creating a new release branch on every minor release (e.g. <code>v1.19.x, v2.0.x, v2.1.x</code>...), we will create one for <strong>every major release</strong>:</p><ul><li>A <strong>v1.x</strong> branch will be created, and security fixes will be backported there</li><li>A new <strong>v2.x</strong> branch will be created, and new releases for v2 will be pushed there</li><li>As we continue to work on NodeBB, we will create additional release branches (e.g. v3.x, v4.x...) as major releases are made</li><li>master will remain the main git branch, but will see less activity, as only bug fixes will be pushed there.</li><li>The develop branch will contain new functionality.</li><li>Every time a minor release is made, develop will be merged into master.</li></ul><h2>What do I have to do?</h2><p>If your NodeBB installation currently tracking a release branch, you can run the following commands:</p><ul><li><code>For v2.x: git fetch &amp;&amp; git checkout v2.x</code></li><li><code>For v1.x: git fetch &amp;&amp; git checkout v1.x</code></li></ul><p>Alternatively, if you wish to pin your installation to a specific version, your best bet is to track the master branch and git reset as necessary:</p><ul><li><code>git fetch</code></li><li><code>git checkout master</code></li><li><code>git reset --hard v2.2.5</code></li></ul><h2>Notes</h2><ul><li>Photo by <a href="https://unsplash.com/@_zachreiner_?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Zach Reiner</a> on <a href="https://unsplash.com/s/photos/branch?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></li></ul>
</div>
</div>
</div>

<hr class="my-5"/>

<!-- FOOTER -->
<footer>
<div class="d-flex flex-column flex-md-row gap-5 justify-content-between mb-5 flex-wrap">
<div class="d-flex flex-column">
<h5 class="fw-bold">Get Started</h5>
<ul class="list-unstyled">
<li><a href="/product" class="link-secondary text-decoration-none">PRODUCT</a></li>
<li><a href="/pricing" class="link-secondary text-decoration-none">PRICING</a></li>
<li><a href="/services" class="link-secondary text-decoration-none">SERVICES</a></li>
</ul>
</div>
<div class="d-flex flex-column">
<h5 class="fw-bold">Resources</h5>
<ul class="list-unstyled">
<li><a href="https://community.nodebb.org/" class="link-secondary text-decoration-none" target="_blank">COMMUNITY</a></li>
<li><a href="https://try.nodebb.org/" class="link-secondary text-decoration-none" target="_blank">DEMO SITE</a></li>
<li><a href="https://community.nodebb.org/category/28/answers" class="link-secondary text-decoration-none" target="_blank">ANSWERS</a></li>
<li><a href="https://docs.nodebb.org" class="link-secondary text-decoration-none" target="_blank">DOCUMENTATION</a></li>
<li><a href="/bounty" class="link-secondary text-decoration-none">BUG BOUNTY</a></li>
</ul>
</div>
<div class="d-flex flex-column">
<h5 class="fw-bold">Company</h5>
<ul class="list-unstyled">
<li><a href="/about" class="link-secondary text-decoration-none">ABOUT</a></li>
<li><a href="/blog" class="link-secondary text-decoration-none">BLOG</a></li>
<li><a href="/contact" class="link-secondary text-decoration-none">CONTACT</a></li>
</ul>
</div>
<div class="d-flex flex-column">
<a href="https://manage.nodebb.org/register" class="btn btn-primary"><i class="fa-solid fa-rocket"></i> Start Free Trial</a>
<div class="d-flex gap-3 mt-3 justify-content-between px-2">
<a title="NodeBB Github Page" href="https://github.com/nodebb/nodebb" class="link-secondary text-decoration-none"><i class="fab fa-github"></i></a>
<a title="NodeBB Twitter Page" href="https://twitter.com/nodebb" class="link-secondary text-decoration-none"><i class="fab fa-twitter"></i></a>
<a title="NodeBB Mastodon Page" href="https://fosstodon.org/@nodebb" class="link-secondary text-decoration-none"><i class="fa-brands fa-mastodon"></i></a>
<a title="NodeBB Facebook Page" href="https://www.facebook.com/NodeBB" class="link-secondary text-decoration-none"><i class="fab fa-facebook"></i></a>
</div>

</div>
</div>
<div class="d-flex flex-wrap justify-content-between gap-5 small">
<span class="text-secondary text-nowrap">©2025 NodeBB, Inc. — Made in Canada with <i class="fa-solid fa-heart text-danger"></i>.</span>
<div class="d-flex gap-3">
<a href="/tos" class="link-secondary text-nowrap text-decoration-none">Terms of Service</a>
<a href="/privacy" class="link-secondary text-nowrap text-decoration-none">Privacy Policy</a>
<a href="/gdpr" class="link-secondary text-nowrap text-decoration-none">GDPR</a>
<a href="/dmca" class="link-secondary text-nowrap text-decoration-none">DMCA</a>
</div>
</div>
</footer>
</div>

<!-- Bootstrap 5 JS Bundle (includes Popper) -->
<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js" crossorigin="anonymous"></script>
</body>
</html>

8
blog/index.html
View file

@ -155,6 +155,14 @@
<p class="card-text">As we hurtle our way through 2022, it’s always good to look introspectively and see how far we’ve gone, and how our goals have changed1. Earlier in the year, I...</p>
</div>
</div>
</div><div>
<div class="card h-100 shadow-sm border-0">
<a href="https://nodebb.org/blog/changes-to-our-release-branches"><img style="height: 225px;" src="https://images.unsplash.com/photo-1521675333836-36e707ac1d20?q=80&w=1740&auto=format&fit=crop&ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D" class="card-img-top"></img></a>
<div class="card-body">
<a href="https://nodebb.org/blog/changes-to-our-release-branches" class="card-title fs-5 fw-semibold text-decoration-none">Changes to our release branches</a>
<p class="card-text">What is a release branch? Whenever we make a NodeBB release, whether it be a patch release, minor release, or a major release, we also push the code to specific...</p>
</div>
</div>
</div><div>
<div class="card h-100 shadow-sm border-0">
<a href="https://nodebb.org/blog/migration-guide-for-v2"><img style="height: 225px;" src="https://images.unsplash.com/photo-1597484661643-2f5fef640dd1?q=80&w=1979&auto=format&fit=crop&ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D" class="card-img-top"></img></a>

1
blog_source/posts/changes-to-our-release-branches.html Normal file
View file

@ -0,0 +1 @@
<h2>What is a release branch?</h2><p>Whenever we make a NodeBB release, whether it be a patch release, minor release, or a major release, we also push the code to specific <strong>release branches</strong>, for those who wish to subscribe to a specific set of releases.</p><p>For example, an administrator who currently runs v1.18.0 of NodeBB might not want to pull the latest code and upgrade all the way to v2.2.5 (as of this writing). They may want to upgrade to the latest version on the v1.18.x release branch, which is v1.18.6. By tracking the release branch, they are safe from accidentally upgrading to a potentially breaking version of NodeBB.</p><h2>Why the change?</h2><p><a href="https://nodebb.org/blog/plugin-compatibility-semver/">Up until recently, we released new versions when we felt it was safe to do so</a>. A patch version could contain new functionality <em>in addition to bug fixes</em>, and minor versions contained breaking changes. A major version bump denoted a radical change (e.g. <a href="https://nodebb.org/blog/migration-guide-for-v2/">the switch to webpack</a>.)</p><p>However, lumping in enhancements and bug fixes meant that occasionally, regressions and unexpected behaviour could occur during upgrades.</p><p>Since the dawn of version 2.0, we wanted to accelerate our release schedule, and remove any roadblocks to a patch release. More information is provided in the <a href="https://nodebb.org/blog/plugin-compatibility-semver/">semver blog post</a>, but in short:</p><ul><li>Patch versions contain bug fixes only</li><li>Minor versions contain bug fixes <em>and enhancements</em></li><li>Major versions contain breaking changes</li></ul><h2>What's the change?</h2><p>Instead of creating a new release branch on every minor release (e.g. <code>v1.19.x, v2.0.x, v2.1.x</code>...), we will create one for <strong>every major release</strong>:</p><ul><li>A <strong>v1.x</strong> branch will be created, and security fixes will be backported there</li><li>A new <strong>v2.x</strong> branch will be created, and new releases for v2 will be pushed there</li><li>As we continue to work on NodeBB, we will create additional release branches (e.g. v3.x, v4.x...) as major releases are made</li><li>master will remain the main git branch, but will see less activity, as only bug fixes will be pushed there.</li><li>The develop branch will contain new functionality.</li><li>Every time a minor release is made, develop will be merged into master.</li></ul><h2>What do I have to do?</h2><p>If your NodeBB installation currently tracking a release branch, you can run the following commands:</p><ul><li><code>For v2.x: git fetch &amp;&amp; git checkout v2.x</code></li><li><code>For v1.x: git fetch &amp;&amp; git checkout v1.x</code></li></ul><p>Alternatively, if you wish to pin your installation to a specific version, your best bet is to track the master branch and git reset as necessary:</p><ul><li><code>git fetch</code></li><li><code>git checkout master</code></li><li><code>git reset --hard v2.2.5</code></li></ul><h2>Notes</h2><ul><li>Photo by <a href="https://unsplash.com/@_zachreiner_?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Zach Reiner</a> on <a href="https://unsplash.com/s/photos/branch?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></li></ul>

14
blog_source/posts/changes-to-our-release-branches.json Normal file
View file

@ -0,0 +1,14 @@
{
"url": "https://nodebb.org/blog/changes-to-our-release-branches",
"title": "Changes to our release branches",
"subtitle": "",
"excerpt": "What is a release branch? Whenever we make a NodeBB release, whether it be a patch release, minor release, or a major release, we also push the code to specific...",
"cover": "https://images.unsplash.com/photo-1521675333836-36e707ac1d20?q=80&w=1740&auto=format&fit=crop&ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D",
"pubDate": "Tue, 26 Jul 2022 18:18:20 +0000",
"author": {
"name": "Julian Lam",
"url": "https://community.nodebb.org/user/julian",
"image": "https://community.nodebb.org/assets/uploads/profile/uid-2/2-profileavatar-1738544541106.jpeg"
},
"content": "changes-to-our-release-branches.html"
}