Skip to content

Conversation

@edsiper
Copy link
Member

@edsiper edsiper commented Jan 5, 2026


Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Summary by CodeRabbit

  • Documentation
    • Updated maintenance policy: v5.0 is now the active development line, v4.2 is the current stable branch (recommended for production), v4.1 continues under maintenance, and v4.0 reached end-of-life
    • Clarified backport process and updated support timelines for applicable versions

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Jan 5, 2026

📝 Walkthrough

Walkthrough

Updates MAINTENANCE.md to establish v5.0 as the active development branch, introduces v4.2 as the new stable series, and updates v4.1 maintenance timelines. Updates SECURITY.md to mark version 4.0.x as end-of-life as of December 23, 2025, while maintaining 4.1.x as active.

Changes

Cohort / File(s) Summary
Documentation Updates
MAINTENANCE.md
Restructures maintenance policy to reflect new development lifecycle: v5.0 master development, v4.2 as current stable series, v4.1 as maintenance branch with updated EOL/Security timelines. Adds explicit guidance for backport targets and multi-branch maintenance workflow.
Supported Versions Update
SECURITY.md
Updates Supported Versions table: marks version 4.0.x as EOL (December 23, 2025); version 4.1.x remains Active.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

Suggested labels

docs-required

Suggested reviewers

  • patrick-stephens
  • fujimotos

Poem

🐰 The versions hop and leap ahead,
v5.0 leads, v4.2 is bread,
And v4.1 takes its final bow,
While 4.0 says goodbye for now! 🌿

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title accurately summarizes the main changes: updating branch information and security EOL details, which aligns with modifications to MAINTENANCE.md and SECURITY.md.
✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@edsiper edsiper changed the title maintenance: update branch info and security EOL info maintenance: update branch and security EOL info Jan 5, 2026
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
MAINTENANCE.md (1)

33-37: Minor: Consider rewording to avoid repetitive sentence beginnings.

The subsection headings (lines 33 and 39) introduce v4.1 and v4.0, but the opening paragraphs reiterate the version, creating awkward rhythm. Smoother alternatives:

🔎 Suggested rewording

For v4.1 (lines 33–37):

 ### v4.1 Maintenance
 
-**v4.1** has entered **maintenance mode**, now maintained by [Hiroshi Hatake (@cosmo0920)](https://github.com/cosmo0920), a long-time Fluent Bit contributor and core developer.
+Maintained by [Hiroshi Hatake (@cosmo0920)](https://github.com/cosmo0920), a long-time Fluent Bit contributor and core developer, **v4.1** has entered **maintenance mode**.
 
-**v4.1** will receive security updates and critical fixes until **February 28, 2026** (as specified in [SECURITY.md](SECURITY.md)).
+Security updates and critical fixes will be provided until **February 28, 2026** (as specified in [SECURITY.md](SECURITY.md)).

For v4.0 (lines 39–41):

 ### v4.0 Maintenance
 
-**v4.0** reached **End-of-Life (EOL)** on **December 23, 2025** and is no longer maintained. No further security patches or bug fixes will be provided for this version line.
+This version reached **End-of-Life (EOL)** on **December 23, 2025** and is no longer maintained. No further security patches or bug fixes will be provided for v4.0.

Also applies to: 39-41

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9191f70 and ff52532.

📒 Files selected for processing (2)
  • MAINTENANCE.md
  • SECURITY.md
🧰 Additional context used
🪛 LanguageTool
MAINTENANCE.md

[style] ~37-~37: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... Bit contributor and core developer. v4.1 will receive security updates and c...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~39-~39: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ed in SECURITY.md). ### v4.0 Maintenance v4.0 reached **End-o...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (21)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SIMD=On, 3.31.6, clang, clang++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_COVERAGE=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_COMPILER_STRICT_POINTER_TYPES=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_ARROW=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SIMD=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SIMD=Off, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SMALL=On, 3.31.6, clang, clang++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SIMD=Off, 3.31.6, clang, clang++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_JEMALLOC=Off, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SANITIZE_THREAD=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SANITIZE_MEMORY=On, 3.31.6, clang, clang++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SANITIZE_MEMORY=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DSANITIZE_UNDEFINED=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SANITIZE_THREAD=On, 3.31.6, clang, clang++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_JEMALLOC=Off, 3.31.6, clang, clang++)
  • GitHub Check: run-ubuntu-unit-tests (-DSANITIZE_ADDRESS=On, 3.31.6, clang, clang++)
  • GitHub Check: run-ubuntu-unit-tests (-DSANITIZE_UNDEFINED=On, 3.31.6, clang, clang++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_JEMALLOC=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DSANITIZE_ADDRESS=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_SMALL=On, 3.31.6, gcc, g++)
  • GitHub Check: run-ubuntu-unit-tests (-DFLB_JEMALLOC=On, 3.31.6, clang, clang++)
🔇 Additional comments (3)
SECURITY.md (1)

10-11: LGTM!

The version table updates clearly communicate the transition of v4.0.x to EOL status effective December 23, 2025, and maintain v4.1.x as Active until February 28, 2026. These dates align with the maintenance policy revisions in MAINTENANCE.md.

MAINTENANCE.md (2)

9-17: LGTM!

The branch table and maintenance policy intro clearly establish the multi-branch lifecycle: v5.0 as active development, v4.2 as stable, and v4.1 as maintenance. The policy statement is concise and actionable.


19-27: LGTM!

The accepted changes and contribution guidelines are well-structured. The master-first policy (line 25) ensures proper version control hygiene, and the explicit backport targeting syntax (lines 50-53) makes the process unambiguous for contributors. The note about v4.0 being EOL is appropriately placed.

Also applies to: 45-54

@edsiper edsiper merged commit d0eeffb into master Jan 6, 2026
47 checks passed
@edsiper edsiper deleted the maintenance branch January 6, 2026 17:52
@edsiper edsiper added this to the Fluent Bit v4.2.3 milestone Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants