View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
20517Bug reportsComfortUpdatepublic2026-05-19 14:312026-05-20 15:21
ReporterMazi Assigned Totibor.pacalat  
PrioritynoneSeverityminor 
Status closedResolutionwon't fix 
Product Version6.17.x 
Summary20517: Global Settings -> Updates use "Release Candidate" as default setting, should be "Stable" instead
Description

Newer LimeSurvey versions come with a global settings tab for updates. At the drop-down, the default setting is "Release candidate". These versions are often not really stable yet. Thus, I highly recommend to set the default setting to "Stable" so only stable versions are shown to the users as updates. Otherwise, many people will update to an unstable release candidate, causing serious issues to their system.

Steps To Reproduce

(Write here what happened instead)

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)6.17.3
I will donate to the project if issue is resolvedNo
Browser
Database type & versionx
Server OS (if known)
Webserver software & version (if known)
PHP Versionx

Users monitoring this issue

There are no users monitoring this issue.

Activities

Mazi

Mazi

2026-05-19 14:31

updater   ~84833

@DenisChenu, what's your opinion on that?
DenisChenu

DenisChenu

2026-05-19 16:46

developer   ~84840

Default must be stable : always !

No discussion here !
Mazi

Mazi

2026-05-20 10:20

updater   ~84862

@tibor.pacalat, can you please address this?
Thanks!
tibor.pacalat

tibor.pacalat

2026-05-20 15:00

administrator   ~84866

After consulting with our internal team, we decided that we will not change this. If you don't want to see the notification, you can change it to stable.
Furthermore, it is also clearly marked as unstable everywhere.
Mazi

Mazi

2026-05-20 15:21

updater   ~84867

@tibor.pacalat, are you serious?!

What is the benefit of having lots of users update to an unstable RC version because of this?!

Issue History

Date Modified Username Field Change
2026-05-19 14:31 Mazi New Issue
2026-05-19 14:31 Mazi Note Added: 84833
2026-05-19 14:31 Mazi Bug heat 0 => 2
2026-05-19 16:46 DenisChenu Note Added: 84840
2026-05-19 16:46 DenisChenu Bug heat 2 => 4
2026-05-20 10:20 Mazi Note Added: 84862
2026-05-20 15:00 tibor.pacalat Note Added: 84866
2026-05-20 15:00 tibor.pacalat Bug heat 4 => 6
2026-05-20 15:00 tibor.pacalat Assigned To => tibor.pacalat
2026-05-20 15:00 tibor.pacalat Status new => closed
2026-05-20 15:00 tibor.pacalat Resolution open => won't fix
2026-05-20 15:21 Mazi Note Added: 84867