Splitting off UsersGuides/ReleaseNotes

[HansOlsson]

To make it easier to track changes.
As discussed at the MAP-Lib meeting.
Also to be cherry picked to maint/4.1.0

[beutlich]

The disadvantage of such a file modularization is that we lose track of the git history. But given that we rather add new classes to the ReleaseNotes.mo it might be accpetable.

[Harisankar-Allimangalath]

@casella @HansOlsson @beutlich so does the present structure looks good and can we proceed with an approval ?

Thankyou

[casella]

This was automatically generated by Dymola, so I trust the content should be ok

[GallLeo]

Fine, as discussed in MAP-LIB meeting.

[Harisankar-Allimangalath]

@HansOlsson @GallLeo @casella , we have to backport this to maint/4.1.x right , just a doubt as the milestone is changed . ?

Thanks

[beutlich]

Also to be cherry picked to maint/4.1.0

I doubt it is necessary.

as the milestone is changed

• If merged to master the milestone must not be MSL4.1.0.
• I merged to master and also cherry-picked to maint/4.1.x, the milestone must not be set at all (since it should only occure in the release notes of the release where it occurred first).

[Harisankar-Allimangalath]

@beutlich @casella @HansOlsson @GallLeo just clarifying my doubt and understanding the scenario , this change is not yet cherrypicked to the maint/4.1.x and we already have a branch which is contains the release note edits and is having the old structure . so we have to cherypick this change to that branch also . (or merge the maint/4.1.x to the releasenotes branch after backporting , which ever is better ) , and something of the above two has to be done right ?