Trac2GitHub Transition of Modelica Assocication Projects

**Comment by hansolsson on 12 Nov 2015 10:23 UTC** Replying to [comment:27 sjoelund.se]: > Pre-release version numbers work rather OK for us in OpenModelica using git. For example: v1.9.4-dev.473+gea54626: 1.9.4...

**Comment by sjoelund.se on 12 Nov 2015 10:47 UTC** > If you rely on the git-hash to disambiguate versions you are not following semantic versioning (depending on version that is...

**Modified by beutlich on 7 Dec 2017 11:26 UTC**

**Comment by sjoelund.se on 3 Mar 2016 16:43 UTC** I forgot to mention it in the description: the feature would be optional for a Modelica tool to implement (which is...

**Modified by beutlich on 3 Mar 2016 18:05 UTC**

**Comment by hansolsson on 4 Mar 2016 09:17 UTC** I believe this is an important extension - especially for FMUs. The simplest case is just an Integrator as co-simulation FMU,...

**Comment by hansolsson on 4 Mar 2016 17:42 UTC** Before I forget, just a minor question: is save-restore a good pair of names, or would save-load, store-restore, or save-resume be...

**Comment by stefanv on 4 Mar 2016 17:47 UTC** To me, it's a toss-up between save/restore and save/resume. I don't like save/load because they imply saving and loading something static...

**Comment by choeger on 5 Mar 2016 12:34 UTC** I do not think it would be very wise to expose the serialized data to the user directly (i.e. have an...

**Comment by hansolsson on 6 Mar 2016 19:26 UTC** To be genuine useful I think we should aim for the possibility of restoring the object to the same state -...