Merged
Conversation
nwt
approved these changes
Mar 3, 2023
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.
I see no functional changes in Brimcap itself since we tagged v1.3.0 just a few weeks ago. However, since Brimcap uses Zed for shaping, there's a chance that a user could try to do some shaping and want to take advantage of some of the things we've already fixed/improved as called out in brimdata/super#4419. Therefore since we're about to put out the Zui v1.0 release I figure it's worth tagging an up-to-date Brimcap that we could point at, hence an update to the changelog.
v1.3.0...ef96c35