[GH-ISSUE #57] LTS version #36

New issue

Closed

opened 2026-03-04 12:18:14 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 12:18:14 +03:00

Owner

Originally created by @dvershinin on GitHub (Aug 2, 2021).
Original GitHub issue: https://github.com/ADD-SP/ngx_waf/issues/57

There have been fast "breaking" releases over time.

By breaking I mean primarily those which introduced some library dependency (e.g. libinjection), or a program (e.g. flex) during compile time.

Can we have a version line, e.g. 6.x which would be updated with any fixes, but not have "breaking" releases?

E.g. new versions will be released but a specific branch like 6.x would incorporate important fixes, while not having many moving parts.

An example is Varnish Cache. The last version is 6.6.1 (some ABI/breaking changes are OK in there), while the last LTS version is 6.0.8 (all versions 6.0.x are LTS and include only important security/bug fixes).

Background: making RPM packages, but builds of newer versions constantly fail due to "yet another dependency change".

Originally created by @dvershinin on GitHub (Aug 2, 2021). Original GitHub issue: https://github.com/ADD-SP/ngx_waf/issues/57 There have been fast "breaking" releases over time. By breaking I mean primarily those which introduced some library dependency (e.g. libinjection), or a program (e.g. flex) during compile time. Can we have a version line, e.g. 6.x which would be updated with any fixes, but not have "breaking" releases? E.g. new versions will be released but a specific branch like 6.x would incorporate important fixes, while not having many moving parts. An example is Varnish Cache. The last version is 6.6.1 (some ABI/breaking changes are OK in there), while the last LTS version is 6.0.8 (all versions 6.0.x are LTS and include only important security/bug fixes). Background: making RPM packages, but builds of newer versions constantly fail due to "yet another dependency change".

kerem

2026-03-04 12:18:14 +03:00

closed this issue
added the
enhancement

timeout
labels

kerem commented

2026-03-04 12:18:15 +03:00

Author

Owner

@ADD-SP commented on GitHub (Aug 3, 2021):

Good idea, I've released v6.1.x as LTS. Meanwhile, I've explained in the changelog what the "breaking changes" are.

You can read about the two release flows (LTS and Current) maintained by this project here.

If you have suggestions, let's continue the discussion, otherwise please close this issue.

@ADD-SP commented on GitHub (Aug 3, 2021): Good idea, I've released `v6.1.x` as LTS. Meanwhile, I've explained in the [changelog](https://add-sp.github.io/ngx_waf/changes/lts.html) what the "breaking changes" are. You can read about the two release flows (LTS and Current) maintained by this project [here](https://add-sp.github.io/ngx_waf/changes/overview.html). If you have suggestions, let's continue the discussion, otherwise please close this issue.

kerem commented

2026-03-04 12:18:15 +03:00

Author

Owner

@ADD-SP commented on GitHub (Aug 4, 2021):

I forgot to mention that branch lts corresponds to the LTS version and branch current corresponds to the Current version.

@ADD-SP commented on GitHub (Aug 4, 2021): I forgot to mention that branch `lts` corresponds to the LTS version and branch `current` corresponds to the Current version.

kerem referenced this issue

2026-03-04 12:19:04 +03:00

[PR #36] Update Dockerfile.alpine #122

kerem referenced this issue

2026-03-13 17:08:17 +03:00

[PR #36] [MERGED] Update Dockerfile.alpine #238