Splitting off UsersGuides/ReleaseNotes

modelica / ModelicaStandardLibrary

Free (standard conforming) library to model mechanical (1D/3D), electrical (analog, digital, machines), magnetic, thermal, fluid, control systems and hierarchical state machines. Also numerical functions and functions for strings, files and streams are included.

https://doc.modelica.org

BSD 3-Clause "New" or "Revised" License

452 stars 165 forks source link

Splitting off UsersGuides/ReleaseNotes #4355

Closed HansOlsson closed 2 months ago

HansOlsson commented 3 months ago

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

Harisankar-Allimangalath commented 3 months ago

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

Thankyou

Harisankar-Allimangalath commented 2 months ago

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

Thanks

beutlich commented 2 months ago

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 commented 2 months ago

@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 ?