Note that BEF/AFT definition language changed from 5.5.1 to 7.0 - #793
Open
tychonievich wants to merge 1 commit into
Open
Note that BEF/AFT definition language changed from 5.5.1 to 7.0#793tychonievich wants to merge 1 commit into
tychonievich wants to merge 1 commit into
Conversation
As proposed in #397, this updates the changelog retroactively to note the changed wording to define `BEF` and `AFT`.
tychonievich
requested review from
albertemmerich,
dthaler and
lynchrs3
as code owners
August 4, 2026 17:58
dthaler
reviewed
Aug 7, 2026
|
|
||
| - Name pieces are not comma separated. | ||
|
|
||
| - The use of "after" and "before" in defining date ranges was ambiguous, with users in some regions interpreting "after 1830" to mean after the *end* of 1800 and others to mean after the *beginning* of 1800, often with each believing their interpretation is the obvious linguistic meaning and not thinking it is ambiguous. To help resolve this, 7.0 now uses "no earlier than" and "no later than" instead, which seems to be consistently interpreted by people from many regions and is inclusive of both previous meanings. |
Collaborator
There was a problem hiding this comment.
Suggested change
| - The use of "after" and "before" in defining date ranges was ambiguous, with users in some regions interpreting "after 1830" to mean after the *end* of 1800 and others to mean after the *beginning* of 1800, often with each believing their interpretation is the obvious linguistic meaning and not thinking it is ambiguous. To help resolve this, 7.0 now uses "no earlier than" and "no later than" instead, which seems to be consistently interpreted by people from many regions and is inclusive of both previous meanings. | |
| - The use of "after" and "before" in defining date ranges was ambiguous, with users in some regions interpreting "after 1800" to mean after the *end* of 1800 and others to mean after the *beginning* of 1800, often with each believing their interpretation is the obvious linguistic meaning and not thinking it is ambiguous. To help resolve this, 7.0 now uses "no earlier than" and "no later than" instead, which seems to be consistently interpreted by people from many regions and is inclusive of both previous meanings. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As proposed in #397, this updates the changelog retroactively to note the changed wording to define
BEFandAFT.