Opened 5 years ago

Last modified 3 years ago

#5714 assigned defect

Build linux stable release only when tagging new versions on maintenance branch

Reported by: Francesco Casella Owned by: Adrian Pop
Priority: critical Milestone:
Component: Installation program Version:
Keywords: Cc:

Description

Currently, the stable release on Linux is re-built every night from whatever is found on the HEAD revisio of the maintenance branch. This is kind of nice because it provides a sort of "nightly build" for beta versions, but on the other hand it is not the same as in Windows and it can be quite confusing, as well as potentially dangerous if something wrong is done on the mainteance branch before tagging a new beta.

I would suggest to only build the Linux version when tagging a new beta release, as implicitly suggested in the download page.

Change History (6)

comment:1 by Francesco Casella, 5 years ago

Owner: changed from Adeel Asghar to Adrian Pop
Status: newassigned

comment:2 by Francesco Casella, 5 years ago

Milestone: 1.14.01.15.0

comment:3 by Francesco Casella, 4 years ago

Milestone: 1.15.01.16.0

Release 1.15.0 was scrapped, because replaceable support eventually turned out to be more easily implemented in 1.16.0. Hence, all 1.15.0 tickets are rescheduled to 1.16.0

comment:4 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:5 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:6 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.