[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Heads up, GPSD release 3.12 is imminent
From: |
Greg Troxel |
Subject: |
Re: [gpsd-dev] Heads up, GPSD release 3.12 is imminent |
Date: |
Sun, 25 Jan 2015 19:17:02 -0500 |
User-agent: |
Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.4 (berkeley-unix) |
"Eric S. Raymond" <address@hidden> writes:
> Greg Troxel <address@hidden>:
>> For the (broken :-) record, 48h after a substantive change is
>> ridiculous.
>
> Sorry, what substabtive change?
By substantive I mean "anything but whitespace (in other than python) or
documentation".
For example:
commit 431be15fd1130773d0a693a4febe607e24e62109
Author: Eric S. Raymond <address@hidden>
Date: Sun Jan 25 12:44:33 2015 -0500
Also, the qt default change. In that, I think the changing of libQgpsmm
is wrong; it's deprecated and so should be off by default. But I think
that won't change behavior.
- ("libQgpsmm", False, "build QT bindings (deprecated alias)"),
- ("qt", False, "build QT bindings"),
+ ("libQgpsmm", True, "build QT bindings (deprecated alias)"),
+ ("qt", True, "build QT bindings"),
As I've said before, my notion is that there should be not only a
feature freeze, but a freeze on any non-doc change except those which
are necessary to fix regresssions, and this period should be at least 7
days. You may have time in the next 48h, but that is likely not to line
up with everyone else's free time.
pgpoShQYsIqD0.pgp
Description: PGP signature
Re: [gpsd-dev] Heads up, GPSD release 3.12 is imminent, Greg Troxel, 2015/01/25