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

Check whether optional new features can be added to 3.0 as a minor release #1632

Closed
pmai opened this issue Jan 19, 2022 · 1 comment · Fixed by #1659
Closed

Check whether optional new features can be added to 3.0 as a minor release #1632

pmai opened this issue Jan 19, 2022 · 1 comment · Fixed by #1659
Milestone

Comments

@pmai
Copy link
Collaborator

pmai commented Jan 19, 2022

From the Design Meeting on 2022-01-19: Go through planned optional features, like fast pointer-based variable access #515, or enhanced step-size agreement for intermediate update, and check whether the current wording in the FMI 3.0 standard would properly allow adding them as optional features in a 3.1 release.

@pmai
Copy link
Collaborator Author

pmai commented Jan 25, 2022

As discussed in the plugfest session on 2022-01-25, this can be done for all of the currently envisioned features with the following clarifcations/enhancements:

The only restrictions that we see is that supporting e.g. sparse arrays (#1098) it might be that one would want/need non-backward compatible changes to things like start values that are already in 3.0; those would need to be performed in a major release.

@t-sommer t-sommer modified the milestones: v3.0, v3.0-rc.1 Jan 31, 2022
@andreas-junghanns andreas-junghanns linked a pull request Feb 2, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants