The PLCgen code generator is near a point where core functionality is feature complete. Next steps are more about extending and improving functionality. As such, a new phase in the development seems to be reached. It's likely that some things are still broken or don't work as expected or should work differently. Finding these problems is more effective if other people can try the generator as well. So the question is what should be done to reach this point. The following seems useful: - [x] Verify that #397 has no core features that must be in the program before a first release. - [x] Update precondition checker for features considered in #397, but that are now out of scope for the first release. (!689) - [x] Make the application usable from the GUI. (!690) - [x] Write some documentation how to use it and other useful information for this version. Mark the application as experimental / work in progress. - [x] Deal with the `PlcFormalFuncInvokeArgOption`, `PlcFormalFuncInvokeFuncOption`, and `PlcMaxIterOption` options of the program. (!697) ~~They should be implemented, or be ...~~ ~~They are postponed to #679 (in !675).~~ - [x] Ensure that remaining points in #397 are added to the follow-up tracking issue #679. - [x] Ensure that points that have come up (at least the TODO list currently hidden in the code) are added to the follow-up tracking issue #679. - [x] Add a `plcgen` ToolDef function. Implemented in !674. - [x] For %v3.0, close #382 and !357. Also delete the `382-add-plcgen0` branch as closing won't delete it. And remove the 'sticky' build for it in Jenkins. (We've put #382 in %"v3.0" and added these steps there.) For next steps after the first release, see #679. Closes #397