Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.0.1 meta issue #604

Open
jsiwek opened this issue Sep 27, 2019 · 1 comment

Comments

@jsiwek
Copy link
Member

commented Sep 27, 2019

Just collecting a list of things targeted for 3.0.1 so we have a separate reminder to port/merge them to release/3.0. Can of course do that gradually over time as things get finished, just find it easier to track in a central location since they'll likely land in master at different times. The alternative of depending on people to create PRs against release/3.0 also seems similarly scattered and error-prone, but open to ideas on how to best organize.

  • #598: to_json() support for set with composite keys
  • #615: add print_raw() BIF as convenience/workaround for #596
  • #595: json logging performance regression
  • #602: external plugins can't find paraglob header
  • #593: sub-microsecond interval descriptions (also needs cde2807)
  • bc18ca4: ptr_func Xcode compiler warnings
  • zeek/broker#58: broker Xcode compiler warnings
  • #591: set[enum] options don't work
  • #606: ambiguous json format for vectors with null elements
    • not a regression as 2.6.4 did a different thing that was also wrong, but still clearly a bug to fix
  • #611: memory leak and "incorrect" field order in RecordVal JSON formatting
  • #632: fix redef of table to use a different &default value
  • #621: just the commit that fixes the tcp_option event
    • "not important enough"
  • #596: allow print to output utf-8
    • Original thought was there's a regression between 2.6.4 and 3.0.0 because the former outputs a valid json format using print to_json(s) while the later may now output invalid json. But changing the default semantics of print may be a breaking change in some contexts (e.g. external plugin unit tests), so safer to target 3.1.0 rather than 3.0.1. Also, technically 2.6.4's version of print doesn't generally guarantee valid json formatting of arbitrary string data, so users should not be using it for that purpose in the first place.
  • maybe zeek/broker#67
@jsiwek jsiwek added this to the 3.0.1 milestone Sep 27, 2019
@jsiwek jsiwek self-assigned this Sep 27, 2019
@jsiwek jsiwek added this to Unassigned / Todo in Release 3.0.1 via automation Sep 27, 2019
@jsiwek jsiwek moved this from Unassigned / Todo to Assigned / In Progress in Release 3.0.1 Sep 27, 2019
@timwoj

This comment has been minimized.

Copy link
Contributor

commented Oct 3, 2019

#615: add print_raw() BIF as convenience/workaround for #596

That can be removed since we decided to close that PR, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Release 3.0.1
  
Assigned / In Progress
2 participants
You can’t perform that action at this time.