There is a discrepancy between the release tags on Github and the downloads page [1].

For example yesterday you released LTS version 3.27.12 which is available on [1]. However, at the same time yesterday on Github [2] you created the release tag for the previous version 3.27.11. It seems that the release tags on Github are always one version behind.

Is this intended behaviour or might there be a mistake in a post release script?

[1] community.limesurvey.org/downloads/
[2] github.com/LimeSurvey/LimeSurvey/releases

I noticed this too and am curious about what the system is with releases on Github.

We're on the 5.1.3 release (which is advertised as the current release at community.limesurvey.org/downloads/ ) but there is no release tagged on Github for 5.1.3.

The last tag I can see, as of right now, is 5.1.2+210813 that was added 2 days ago.

It would be great if the release on Github was in sync, as we'd like to do something like this with 5.1.3:

```
git fetch -unf origin [TAG]:refs/tags/[TAG]
git checkout [TAG]
```

The developers responsible for this are not that frequently in the forum. I will see if I can ping them to see if they can have a look at this.

Looks weird to me.

But it could be because the last release was basically an "emergency release" due to some problems with comfort update. So maybe the fix was only sent through comfort update and on the download section for those that needed to fix it, while it was not included in Github.

Just a wild guess.

Okay great, thanks for that.

I noticed the same happened again with the release from yesterday.

Advertised on [1] the latest release is 3.27.13 from 23.08.2021. On Github, however, the latest release is tagged 3.27.12+210816 and the tag was created on 23.08.2021.

[1]  community.limesurvey.org/downloads/

Hi!

I heard back from Limesurvey support and here is what they said:

Our GitHub version is always one version below the version on our download page.

It is not due to the comfort-update issue.

Sorry, had received the feedback end of last week already, but forgot to post it here.

Thanks for getting back.

*Why* is the "GitHub version is always one version below the version on our download page"?

*Why* is the "GitHub version is always one version below the version on our download page"?

No idea.

My opinion : to «force» to pay comfortupdate ?

My opinion : to «force» to pay comfortupdate ?

Didn't want to say it...

So you are running crippleware... damn, that sucks.

Not sure how you define cribble ware. You can use limesurvey completely for for free on your server and you can download the newest version. Comfort update is a paid service, but you can use the software without it totally fine. You can download the latest version from the download section, it is available at the same time as in comfort update. I don't see it as cribble ware.

The common definition: "Software that has some important functionality deliberately removed, so as to entice potential users to pay for a working version." Or "software products whose [sic] functions have been limited (or "crippled") with the sole purpose of encouraging or requiring the user to pay for those functions..."

en.wikipedia.org/wiki/Crippleware

Systematically holding back an entire release on Github to make updating more difficult fits the definition of crippleware.

Call it what you want. You can get the full software by downloading it from the site and you can update it anytime, the same way you update a lot of other web software.
You are getting the software with all features for free if you install it on your own server. I find that a pretty good deal.

So either you download the zip file with the latest version or you wait a couple of days and get it via github. 

Anyway, I am out. If you want to complain, send an email to the core developers, or make a bug report, or something. Most of us here in the forum are users helping other users. 

nooblag wrote:

Systematically holding back an entire release on Github to make updating more difficult fits the definition of crippleware.
 

With LTS : i just git update all night …
There are no «has some important functionality deliberately removed»