This post contains several issues from the CalculiX GitHub repository that have been closed due to our new issue policy ( Issue policy on GitHub · Issue #158 · Dhondtguido/CalculiX · GitHub ) and were transferred here.
@Durbul If there’s a GitHub report with an example file, but no forum thread (it wasn’t required before, and many long-term users just reported directly on GitHub when a bug was obvious), then I would leave it there. I doubt there will be any additional action taken for these old issues here, and they will need to go back to GitHub anyway. So I think that the new policy shouldn’t apply equally to old issues. I would only clean up issues that are not bug reports or feature requests (such as information about various applications of CalculiX and 3rd party tools related to it) and maybe bug reports with no example files (I think that most have them, though).
I’ll leave the existing bug reports (most of them have a minimal working example, so it’s easy to confim they are still relevant). But I’ll close and transfer those to Discourse (such as the two above) that are still possibly relevant, but not specific enough to serve as a basis for a concrete fix or implementation (for feature requests).
I hope this makes sense.
Ok, thanks, this is exactly what I meant. Reports with attached/linked input decks are indeed easy to confirm and retest in a new version of CalculiX.