Jeff's initial 1.7 changes #62
Merged
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
…ually in version 1.6), 64, 65, and 69. Thus this corresponds to the 1.7 draft which I had previously implemented in DocBook.
…ring this Asciidoc version up to the level of the DocBook version.
|
cc @JonathanGregory, @JohnLCaron, @rsignell-usgs in case any of you have merge rights. |
|
Please could someone add the 1.7 milestone to this PR. |
Closed
| | `mode` | __u__ | Mode (most common value) | ||
|
|
||
| | `range` | __u__ | Absolute difference between maximum and minimum | ||
|
|
||
| | `root_mean_square` | __u__ | Root mean square (RMS) |
There was a problem hiding this comment.
|
this covers all the changes required by the referenced trac tickets and no unreferenced changes thank you |
|
🎉 Our first non-trivial change. 😁 |
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.
Just in case it helps "unstick" the 1.7 preparation process I've created this PR with the commits that @painter1 had accrued on the
1.7.1branch on the main repo.(Who can merge PRs? The list of people in the cf-convention organisation seems to leave out quite a few! It might help for the members to make themselves public?)
Closes #59