-
Notifications
You must be signed in to change notification settings - Fork 357
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
Collect all information on changes in "what's new" #2463
Conversation
Should the section on pre_run_hook / calibrate be removed entirely if its developer focused? I think the release notes provided on GitHub should suffice for developers. What do you think? |
Done with 56fec6d. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@heplesser I spotted a couple of minor typos, but otherwise looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks good now.
This PR collects information on changes in NEST 3.4 in the "what's new" section and removes the "release_notes" directory.
It also restructures the "What's new" file to make changes that modify NEST behavior more visible and separate information only relevant for NEST developers from information relevant for users.
Since
calibrate()
/pre_run_hook()
are C++ methods, they are no longer labeled aspy:func:
.