modelica
Setting master version to 4.2.0 dev
Setting version to 4.2.0 (also ModelicaTest, Complex, etc. - hope I didn't forget one) and provide ReleaseNotes.mo for 4.2.0, including the already merged OpAmp (#4643 and #4653)
Thanks @maltelenz I wasn't aware of these tiny whitespace changes. Without discussing tool issues in public: I didn't touch these parts of MSL and I don't know how to avoid these changes. I hope I have addressed them all. Sorry I did this myself because I wasn't logged in at github and therefore I didn't see that I could accept your suggestions easily ...
Without discussing tool issues in public: I didn't touch these parts of MSL and I don't know how to avoid these changes.
Perfectly preserving whitespace when editing is a very hard problem for a tool, so whichever tool you used I don't blame it :)
I try to discard small changes like these before committing, but they can slip through the cracks easily.
To be honest, I would prefer "4.2.0 dev" - you see even later it had been taken from master.
To be honest, I would prefer "4.2.0 dev" - you see even later it had been taken from master.
If that's the consensus, I'm OK with that, even if I prefer to keep to cleaner version numbers.
I realized that I hadn't mentioned that the Modelica Language specification has explicit support for pre-release versions: https://specification.modelica.org/master/annotations.html#version-numbering
Since we have agreement that the development version is named 4.2.0 and we need a proper version number as well as the table for the release notes -> merging.