i'm a little bit confused about LS versioning: i see posts concerning 2.5X, 2.6, 3 and also older ones (1.92, 2.06) which are more easy to understand.
recently started a project with 2.5x. how long is this version supported?
are there upgrade procedures for the next version?
when the 3.x version is planned to launch?

So far the upgrade to the next version is usually covered, especially if you use the comfortupdate. If you don't upgrade for a few versions, you might have to make the upgrade in steps.

A version is usually supported until the next version comes out. Currently there is an exception with 2.06 LTS, which is longer supported.

What do you mean about supported ?

In forum : if an user want to help you : it's a "no version" support. I still answer for some 1.91 or 2.05 version.

For the warranty : there are no warranty : github.com/LimeSurvey/LimeSurvey/blob/ma...docs/license.txt#L10

I support any version for my client. Sometimes put a fix on a 2.00 or 2.05 version : they have a warranty by me, not by limesurvey.

See more version like "branch", there have actually 4 different branch used
- Before 1.92 branch : this user MUST update, because it's really more easy to do something in new branch
- 1.92 version branch : user take risk to use this branch (security issue) , but functionnality are here. Better to use a newer branch
- 2.05/06/6 branch : this is the same branch : user can update to 2.6.1ltl or any fork updated .
- 2.5X branch : actual master/stable version
- 3.0 version : develop version , in alpha private currently. SOme week ago, i think it was in alpha public in december, but now .... maybe in february ...

i'm new to LS. usually cms like drupal, have a stable release, an oldstable and a dev version. when the dev version becomes stable, the oldstable is not maintained anymore (no security updates).
that was my question. in LS terms, is there an estimation when the branch 2.5X will become like 1.92? no security fixes, andthe user must update?

Drupal VS LimeSurvey contributor .....

Person : github.com/LimeSurvey/LimeSurvey/graphs/contributors (87) vs www.drupalcores.com/ (3824)

Companies for Drupal : www.drupalcores.com/companies.html
For LimeSurvey : we have a lot of big company using it, less contribute to it.

Else : it's a LimeSurvey Gmbh for 2.6 branch (lts).

holch wrote: A version is usually supported until the next version comes out. Currently there is an exception with 2.06 LTS, which is longer supported.

The main source of confusion is that the OLD 2.06 LTS is now 2.6.1 LTS. 2.5 is not a version in-between. It is a different branch.
The newer, refactored branch started with LS 2.5 and is now at LimeSurvey 2.57.0 build 161202.
I still don't know why this renaming was needed.

jelo wrote: The newer, refactored branch started with LS 2.5 ...

No, ther is a missunderstanding here.

It's not 2.5, it's 2.50 (or 2.50.0)

DenisChenu wrote: ]No, ther is a missunderstanding here.
It's not 2.5, it's 2.50 (or 2.50.0)

Yepp, (2.06=2.6 ) but the message won't come across. Since years 2.05 and 2.06 were used.
I would use 2.06.1 instead of 2.6.1 to keep confusion low for the LTS.

There is a lack of sending a clear message. What versioning scheme is LimeSurvey using now.
The old scheme had a date as build-number. With 2.50 the frequency of builds reached the state of more than one per day.
Future dates where used as build-numbers. Shortly afterwards X.YY (2.50) were expanded to X.YY.ZZ. (2.55.2).
Whoever enforced that change has the obligation to communicate the new version schema.
It is not a major.minor.build.revision schema. It's perhaps a major.minor.patch. But who knows?

You totally right .

It's unclear for the 2.06 == 2.6

Else, LimeSurvey moved to semver versionning system semver.org/ then
MAJOR.MINOR.PATCH

during 2.5x , 2.50 don't use semver, 2.51.0 use semver (i think).

I agree that it was confusing, even for me. I think it should maybe not been implemented with current versions, but rather for 3.0 onwards. But hey, we are used to this type of spontaneous decision, without a concern of what impact this will have on "normal" users, aren't we?

So far, I always tried to avoid the topic when someone asked. Because I just didn't know what's behind it. Denis' post shed some light at least.

ok, versioning is clear now.
is there an estimation about supporting 2.5X? as i understand, 2.6.X is the LTS version.

Remind : LimeSurvey is a free tool. For example, i manage a 1.92 security version 8 month after 1.92 is dead.

You can always ask for a professional support of a 2.5X version during 2 years if you want to LimeSurvey Gmbh or another team. But : i don't think it can be free of charge.