Draft
Conversation
Contributor
Author
|
@pnbabu: in order to save some compute time on our (already quite heavy) CI runs, I would propose to change the v3.9 run into the new 3.10 run, and to drop the 3.0 run. Although we would still support NEST versions back to and including 3.0, they would just not run on CI, just like all the other intermediate versions (3.1, 3.2, ..., 3.8). Perhaps we can set this up as a CI run triggered by a monthly timer or so, but only check NEST's "latest release" and "main branch" on every NESTML repo push. What do you think? |
added 2 commits
April 22, 2026 14:26
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
1 participant
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.
No description provided.