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

Add note to expect changes to tripartite syntax and semantics #3128

Merged
merged 3 commits into from
Mar 4, 2024

Conversation

heplesser
Copy link
Contributor

This PR add a note to documentation to alert users about upcoming changes in the syntax and semantics for tripartite connectivity.

@heplesser heplesser added S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation. I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) labels Mar 1, 2024
Copy link
Contributor

@HanjiaJiang HanjiaJiang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. Thank you!

@terhorstd terhorstd added this to the NEST 3.7 milestone Mar 4, 2024
Copy link
Contributor

@jessica-mitchell jessica-mitchell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@heplesser There are a couple of typos to fix, but I approve

doc/htmldoc/synapses/connection_management.rst Outdated Show resolved Hide resolved
pynest/nest/lib/hl_api_connections.py Outdated Show resolved Hide resolved
Co-authored-by: jessica-mitchell <mitchell20j@gmail.com>
@heplesser
Copy link
Contributor Author

@jessica-mitchell I committed your suggestions so feel free to merge once the tests are through.

@jessica-mitchell jessica-mitchell merged commit 4136d6d into nest:master Mar 4, 2024
24 checks passed
@heplesser heplesser deleted the add-tripartite-note branch April 24, 2024 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants