[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

✘ Release blockers?

From: Gary E. Miller
Subject: ✘ Release blockers?
Date: Wed, 11 Dec 2019 14:31:20 -0800

Yo Fred!

On Sun, 8 Dec 2019 20:10:40 -0800 (PST)
Fred Wright <address@hidden> wrote:

> On Fri, 6 Dec 2019, Gary E. Miller wrote:
> [...]
> > Anything else that shold be addressed before next release?  
> There are two regressions since the last release that I'm aware of:

One fixed, one to go.  See below.  Any others anyone sees?

> 1) The C++ build breakage related to timespec_str.  I already have a 
> tentative fix for that, but just as I was about to test it, I ran
> into a disk-space issue for my VMs, which I'm in the process of
> sorting out.  The whole C++ area is pretty much a mess, but at least
> this can make it no worse than it used to be.

Any progress?

> 2) The rename of the altitude field has an interoperability issue
> with other GPSD versions.  The client and server can be on different
> machines, and not necessarily the same version.  At least one
> direction should be fixable with a bit of fallback code.

I restored "alr"/"altitude" and marked it deprecated and undefined.

This will be the first gpsd with any forward or backward compatibility
in the JSON.  The release gpsd client will connect to older gpsd server,
with loss of functionality.  Older gpsd clients will not be able to
connect to a newer gpsd server as cross compatibility was never allowed
before James's patch.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

Attachment: pgpz5vAeypvjJ.pgp
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]