Record the 2.1.0 changes in the changelog - #251
Merged
Conversation
2.1.0 is not tagged yet, so a fix for something introduced in the same unreleased cycle has no entry of its own. Those are folded into the entry for the feature they complete, since nobody upgrading ever saw the intermediate state.
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
1 participant
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.
Context and Purposes
2.1.0is written inCHANGELOG.mdbut is not tagged (the latest tag is2.0.1), so everything in that section is still unreleased. Seven pull requests landed today and none of them were recorded.Entries describe the net user-facing change rather than the development history. Where a pull request repaired something introduced in this same unreleased cycle, it gets no entry of its own and is folded into the entry for the feature it completes, because nobody upgrading from
2.0.1ever saw the intermediate state. Two entries were collapsed that way:VTIMEZONEcomponents (Emit VTIMEZONE components for referenced TZIDs #249) and the equivalent zone spellings (Fix: treat equivalent timezones as a single zone #246). Both fixed the feature before it shipped.Three fixes changed behaviour relative to
2.0.1and are listed on their own: the UTC fallback for timezones that name no place (#248), the ICS option injection fix (#245), and the RFC 5545 compliance gaps (#250). The customDTSTAMPoption (#244) is new, and the Yahoo limitation (#243) is documentation.