[Releasing] [Development] brown paper bag issue in Qt 5.6.1 packages

Tuukka Turunen tuukka.turunen at qt.io
Wed Jun 22 13:33:38 CEST 2016


The more there are changes, the more we need to test and the higher the probability of some other things going wrong. If there is only one (or few enough) change to an existing version, we can release binaries in a couple of days e.g. to address a vulnerability or like this case a bad bug.



From: Releasing [mailto:releasing-bounces+tuukka.turunen=qt.io at qt-project.org] On Behalf Of Giuseppe D'Angelo
Sent: keskiviikkona 22. kesäkuuta 2016 11.04
To: Jani Heikkinen <jani.heikkinen at qt.io>
Cc: Thiago Macieira <thiago.macieira at intel.com>; releasing at qt-project.org
Subject: Re: [Releasing] [Development] brown paper bag issue in Qt 5.6.1 packages

On Wed, Jun 22, 2016 at 8:28 AM, Jani Heikkinen <jani.heikkinen at qt.io<mailto:jani.heikkinen at qt.io>> wrote:
In my opinion bumping version numbers and doing totally new release because of just one fix is too heavy. I think we should have a way to produce this kind of update with 'simple hot fix ' easily and quickly without re-doing whole release in case of this kind of blocker.

This reopens a question which is still very obscure to the community (or at least to me), which is: what is the complexity of creating packages? Why is redoing packages with a different version number (say, by branching 5.6.1 into 5.6.2) "too heavy"? Could you please share some insights on what happens behind the scenes?

Thank you,
Giuseppe D'Angelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20160622/8ecfff65/attachment.html>

More information about the Releasing mailing list