ChangeLog, et al., updated Version 3.17.0 #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
!!:shipit:!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first candidate for libdap 3.17.0.
NEWS:
Better error reporting. Error objects are now always thrown with a
code that 'make sense' and use the default code only when really
necessary. This means that the BES will not report most Error throws
as an internal error (only a few are) unless that's really the case.
This is used, in turn, by the front end to make better error responses
for users.
The old timeout code is still present but not used. This matches
changes made in the BES to correctly process timeouts.
Improved support for doxygen.
Support for DAP4: Attributes were sometimes mis-coded as Byte when
they should have been Float32. Fixed.
Child Groups were sometimes printed twice. No more.
I would like to release the code on Monday 1 Feb. Please let me know if you have issues with this code by Friday 29 Jan.
Thanks,
James