Prepare library for inclusion into MSL 4.0.0

[bernhard-thiele]

The Modelica_Synchronous library shall be included in the future MSL 4.0.0 (see modelica/ModelicaStandardLibrary#2862).

The questions is how to do this transition in a good way. I already experimented with simply using the Dymola rename function for moving the library into the package Modelica.ClockedBlocks. This worked without problems. Remaining manual work is updating the documentation and maybe conversion scripts (though I'm not sure if there is a need to automatically convert Modelica_Synchronous blocks to corresponding MSL 4.0.0 blocks).

However, it probably makes sense to first fix issues in the Modelica_Synchronous library before moving the code base into the MSL project. This could be done in an own branch, or in the master branch. An own branch has the advantage that quick experimental changes can be made without affecting or confusing users who rely on the master branch.

That's why I propose to add a new branch (e.g., msl4_0_0) for fixing the issues and preparing the library so that it can be easily transferred into the MSL 4.0.0.

[christoff-buerger]

Fixing issues first sounds good. I have quiet a couple of things in mind that need some cleanup. But I need to find a free week to do some concentrated work (mostly related to the event clock examples).

What is our roughly time-schedule? Which deadlines do you like to set for the fixing-branch?

[bernhard-thiele]

I was roughly thinking about the next two months. There are not many open issues (at least not on the issue tracker).