Skip to content

Recipe: Lucee release cycle and branching - #1568

Merged
michaeloffner merged 6 commits into
lucee:masterfrom
GianTschingt:recipe-release-cycles
Oct 2, 2026
Merged

michaeloffner merged 6 commits into
lucee:masterfrom
GianTschingt:recipe-release-cycles

Conversation

@GianTschingt

Copy link
Copy Markdown
Contributor

Rewrites docs/recipes/release-cycle.md to match the current release process:

  • version format (MAJOR.MINOR.PATCH.BUILD) and suffixes
  • minor branches vs. RC/release branches, and when a release branch is created
  • an RC branch only takes fixes for regressions since the last final release of its line (7.1.1 since 7.1.0, 7.0.6 since 7.0.5, 6.2.9 since 6.2.8); everything else goes to the minor branch for the next cycle
  • merging forward (release branch into minor branch, 7.0 into 7.1 into 8.0), done by the maintainer
  • one PR (fix + test) against the lowest affected branch only
  • Jira fix versions taken from loader/pom.xml at the point the fix first landed on each branch

Removes outdated statements (build number per commit, -rc1 naming, general bug fixes on release branches, example timeline). Index, README and lucee.skill regenerated with .github/scripts/generate-index-recipes.js.

Document version format and suffixes, minor and RC/release branches,
which branch takes regressions vs other fixes, merge-forward order,
single-PR rule for contributors, version bumps and Jira fix versions.
Removes content that contradicted the current process (rcN tags,
per-commit build increments, maintenance/EOL phases).
Regenerate recipes index, README and lucee.skill.
Only an unreleased RC branch takes regressions since the last final;
add a worked example for cycles 7.1.1 and 7.1.2.
Document that 7.0 -> 7.1 -> 8.0 are linked while 6.2 -> 7.0 no longer
is, and that unlinked lines need their own pull request per line.
Restore the maintenance phase (urgent security fixes only, from release
until the next patch release) and end of life from the original recipe,
and reference it from the worked example.
Per Michael: once a release is done its branch gets no more updates and
fixes go into the next cycle. Replace the maintenance/end-of-life section
with a short After a Release section and drop the security-fix exception
from the worked example.
@michaeloffner
michaeloffner merged commit 3587e5b into lucee:master Oct 2, 2026
2 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants