List of supported versions #93

New issue

Open

opened 2025-12-28 17:36:07 +00:00 by sami · 3 comments

sami commented

2025-12-28 17:36:07 +00:00

Owner

Originally created by @alexvanin on GitHub (Nov 30, 2022).

For support/v0.25 branch we decided to set end-of-life with v0.25.1 release and focus on v0.26.0
We need to maintain list of all currently supported versions. So bugfixes will be ported to all relevant support branches.
Feel free to propose the place where we should maintain this list: GitHub Wiki, README, separate md page, anything.

Originally created by @alexvanin on GitHub (Nov 30, 2022). For `support/v0.25` branch we decided to set end-of-life with v0.25.1 release and focus on v0.26.0 We need to maintain list of all currently supported versions. So bugfixes will be ported to all relevant support branches. Feel free to propose the place where we should maintain this list: GitHub Wiki, README, separate md page, anything.

sami added the

enhancement

documentation

help wanted

labels

2025-12-28 17:36:07 +00:00

sami commented

2025-12-28 17:36:08 +00:00

Author

Owner

@KirillovDenis commented on GitHub (Dec 1, 2022):

We can start from README. If such list will be huge we can move it to separate md page

@KirillovDenis commented on GitHub (Dec 1, 2022): We can start from README. If such list will be huge we can move it to separate md page

sami commented

2025-12-28 17:36:08 +00:00

Author

Owner

@alexvanin commented on GitHub (Dec 1, 2022):

@realloc Probably we need to create some document about LTS time slots? How many versions we support, for how long? This should be declared explicitly, I suppose.

Then we can have a list of supported versions in README, e.g.

Version	Link
v1.10.x (unreleased)	master
v1.9.x	support/v1.9
v1.8.x	support/v1.8
v1.5.x (LTS)	support/v1.5

Any other suggestions are appreciated
/cc @KirillovDenis @masterSplinter01 @mike-petrov

@alexvanin commented on GitHub (Dec 1, 2022): @realloc Probably we need to create some document about LTS time slots? How many versions we support, for how long? This should be declared explicitly, I suppose. Then we can have a list of supported versions in README, e.g. |Version | Link | | --- | --- | | v1.10.x (unreleased) | [master](https://github.com/nspcc-dev/neofs-http-gw/tree/master) | v1.9.x | [support/v1.9]() | v1.8.x | [support/v1.8]() | v1.5.x (LTS) | [support/v1.5]() Any other suggestions are appreciated /cc @KirillovDenis @masterSplinter01 @mike-petrov

sami commented

2025-12-28 17:36:08 +00:00

Author

Owner

@realloc commented on GitHub (Dec 1, 2022):

Agree, having a support policy is a must.
I suggest defining LTS releases case by case and provide fixes for the latest release and all supported branches.

@realloc commented on GitHub (Dec 1, 2022): Agree, having a support policy is a must. I suggest defining LTS releases case by case and provide fixes for the latest release and all supported branches.