View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 2
IDProjectCategoryView StatusDate SubmittedLast Update
15273Bug reportsOtherpublic2019-09-12 14:422019-09-16 16:40
Reporteritaxentiva Assigned Toollehar  
PrioritynoneSeveritytrivial 
Status closedResolutionwon't fix 
Product Version3.17.x 
Summary15273: Untagged release 3.17.16 in github
Description

In the github master branch, the commit for the 3.17.16 release was made but is not properly tagged. This may cause troubles in servers where admins have automatic realease warnings based on the github repo.

Steps To Reproduce

You can see in this commit ( https://github.com/LimeSurvey/LimeSurvey/commit/7aaebcbbfc33f9cb532e695f358b416a53fb0a1e ) the realease but then in the view of the realeases it doesn't appear ( https://github.com/LimeSurvey/LimeSurvey/releases )

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

Users monitoring this issue

There are no users monitoring this issue.

Activities

ollehar

ollehar

2019-09-16 16:40

administrator   ~53590

The latest release is always untagged.

Issue History

Date Modified Username Field Change
2019-09-12 14:42 itaxentiva New Issue
2019-09-16 16:40 ollehar Assigned To => ollehar
2019-09-16 16:40 ollehar Status new => closed
2019-09-16 16:40 ollehar Resolution open => won't fix
2019-09-16 16:40 ollehar Note Added: 53590