TODO and NEWS updated for release.

All regression tests pass.  Code splints and cppchecks clean. flocktest passes.

2 files changed, 28 insertions, 19 deletions

diff --git a/NEWS b/NEWS
index 29af3bbd..cbd2de30 100644
--- a/NEWS
+++ b/NEWS
@@ -1,18 +1,18 @@
-* Wed Dec 16 2010 Eric S. Raymond <esr@snark.thyrsus.com> - 2.96~dev
+* Thu Mar 10 2011 Eric S. Raymond <esr@snark.thyrsus.com> - 2.96~dev
   Bumped maximum channel count to 32 to accommodate GPS+GLONASS devices.
-  API version bumped to 5, redesign in progress (changes are documented
+  API version bumped to 5, redesign finished (changes are documented
   in the Client HOWTO). cgps now handles resize signals. Code can now
   link with uClibc for embedded use.  Various bugs in the C++ binding
   have been fixed. gpxlogger can now daemonize and write to a specified
   log file. A gpsd client can now set any locale it likes, and JSON
   will still be parsed using the C locale matching the daemon's.  Clients
   are no longer required to define a gpsd_report() hook. gpsd no longer
-  emits probe strings to unidentified USB devices at startup.  The client
-  API cleanup is finished; set_raw_hook is gone. JSON timestamps in TPV and
-  SKY are now ISO8601 rather than seconds since the Unix epoch. GPGST sentences
-  are now parsed for noise statistics when a device emits them.  AIS and
-  RTCM2 JSON dumps have device fields. JSON reports now include 50bps subframe 
-  data if the device allows access to it. gpsdecode can now dump NMEA
+  emits probe strings to unidentified USB devices at startup. 
+  JSON timestamps in TPV and SKY are now ISO8601 rather than seconds since
+  the Unix epoch; the library handles the old stle backward compatibly. 
+  GPGST sentences are now parsed for noise statistics when a device emits them.
+  AIS and RTCM2 JSON dumps have device fields. JSON reports now include 50bps
+  subframe data if the device allows access to it. gpsdecode can now dump NMEA
   GPS binary, and subframe data to JSON. The RTCM2 code now understands and 
   analyzes RTCM2.3 messages 13 and 14.  The ancient Sager dump format for RTCM2
   is abolished in favor of a JSON profile.
diff --git a/TODO b/TODO
index dfc8c12b..66f44470 100644
--- a/TODO
+++ b/TODO
@@ -107,17 +107,20 @@ packet-cracking needed to get the data off the chips.
 
 Several commodity chipsets (ANTARIS, iTrax3, SiRF and Trimble) readily
 output enough data to make this a chore, rather than a hard problem.
+And pseudoranges, if available, are now part of the SKY report.
 
-It has been suggested one way to do this is to have a generic structure
-in memory and corresponding output message with clock, doppler carrier
-phase and pseudoranges. This message is then reformatted by a client
-program. There are numerous formats for this information, and it would
-be easier to adapt to new formats if the formatting and use was handled
-by something other than the gpsd daemon. Currently the RT-IGS format is
-looking like the favorite for implementation; it's a fairly lightweight
-protocol, flexible enough to handle all the quantities required, and it
-is actually in use in production reference networks. RT-IGS is also a
-packet-oriented format, rather than a file-oriented format like RINEX.
+Probably the best way to do this would be to add support for unscaled
+output of peudoranges in SKY and add clock and doppler carrier
+phase. This message could then be interpreted by a client program.
+
+There are numerous formats for this information, and it would be
+easier to adapt to new formats if the formatting and use was handled
+by something other than the gpsd daemon. Currently the RT-IGS format
+is looking like the favorite for implementation; it's a fairly
+lightweight protocol, flexible enough to handle all the quantities
+required, and it is actually in use in production reference
+networks. RT-IGS is also a packet-oriented format, rather than a
+file-oriented format like RINEX.
 
 *** RTCM3 support.
 
@@ -131,12 +134,18 @@ boundaries right.
 
 ** Future features (?)
 
+*** NOFLOAT build
+
+We want to be able to build a minimalist version that doesn't require
+floating-point arithmetic, for deployment on low-power ARM devices 
+without FPU.
+
 *** Support for more survey / professional / up-scale receivers.
 
 Devices such as the Javad JNSCore, Hemisphere Crescent, Septentrio
 AsteRx and PolaRx, NovAtel Superstar2 and OEMV, Thales (Magellan
 Professional) AC12 and DG14 would all be welcome. Of course, these
-are not $50 usb mice...
+are not $50 USB mice...
 
 *** Audio cues in the client when the fix status changes