[Releasing] Meeting minutes: Qt release team meeting 26.05.2014

Knoll Lars Lars.Knoll at digia.com
Tue May 27 09:52:43 CEST 2014

On 27/05/14 09:44, "Weber Niels" <Niels.Weber at digia.com> wrote:

>Am Dienstag, den 27.05.2014, 06:32 +0000 schrieb Koehne Kai:
>> > > o   Target is to put updated packages (4.8.6-1) available as soon as
>> > > possible (packages ready)
>> >
>> > On the naming: do not use the dash, please. It's either 4.8.7,
>> or 4.8.6b.
>> Could you elaborate?
>> It is exactly 4.8.6 code wise ... all that's changed is the configure
>> arguments that are used to build the binary package. So it really
>> shouldn't be 4.8.7 (we don't tag anything in the sources), and
>> 4.8.6b ... well, I'm not sure whether the Installer Framework can
>> handle this :) I personally find 4.8.6-1 (Qt 4.8.6, build 1) quite
>> intuitive.
>Installer Framework doesn't handle letters, so 4.8.6b is out.
>Usually, the dash numbers are for packagers, not for upstream versions,
>I guess that's what Thiago doesn't like about 4.8.6-1 (and I agree). For
>example the Qt 4 in my Linux distribution is at 4.8.6-5 - now naming a
>release 4.8.6-1 is confusing and makes life harder for packagers. (Yes,
>not that important for Windows, but differing between Windows and Linux
>versions also confuses.)
>Why not just do a

Well, if the sources are identical to 4.8.6, 4.8.6-1 seems to make some
sense, as we’re doing the same thing as packagers (repackage an existing
release). Linux distributions can ignore this release anyway, as they
build Qt on their own.


More information about the Releasing mailing list