New Release? about modelica_devicedrivers HOT 33 CLOSED

Should be released one month ago. I will try to get it done next week (need access to Dymola license to do it... )

from modelica_devicedrivers.

In case we want to have some information on the new release in the upcoming Modelica newsletter we should meet the deadline September 4th. We can use this issue to discusss the content we want to place there. But time is hurrying...

from modelica_devicedrivers.

I have played with some ideas from Mike and @dietmarw about how to organize the release of Modelica libraries that are discussed in this blog.

So, I created a toy "alpha" release at https://github.com/modelica/Modelica_DeviceDrivers/releases. It's not supposed to be visible to the public (unpublished draft), but I think @tbeu and @dietmarw can see it.

@dietmarw Is it already possible to point the link form https://www.modelica.org/libraries to that release page, instead of relying on the "release branch" approach?

from modelica_devicedrivers.

@bernhard-thiele When you check the download links then you will notice that they they now point to the release page rather than to a direct zip URL. I've made this change some month back when reflecting the release process while working on the new impact paper (it's not a blog but our actual paper ;-) ). So we were thinking alike here. People can still use a release branch to create a modified version but what's probably better is simply create a packaged version and upload that to the release pages including some info. Just like you have done.

from modelica_devicedrivers.

I adapted the changelog.

from modelica_devicedrivers.

@dietmarw That's great, feels more natural than having that release branch. Thanks!

from modelica_devicedrivers.

I just noticed that I should have updated the paper for the final version that the new way is already in place ... too late now.

from modelica_devicedrivers.

Should not be too late if you ask @sjoelund directly.

from modelica_devicedrivers.

Yes, just had a chat with @dietmarw and explained, that it can be arranged ...

from modelica_devicedrivers.

And M_DD is not the only lib considering this ideas. 😏

from modelica_devicedrivers.

Done: impact/impact@dad21e2#diff-bb7e8a08cb26f6ff0c5ca32a7e34db3f

from modelica_devicedrivers.

In case we want to have some information on the new release in the upcoming Modelica newsletter we should meet the deadline September 4th. We can use this issue to discusss the content we want to place there. But time is hurrying...

Any news on this?

from modelica_devicedrivers.

There is now a release draft for 1.4.0.

The zip file was generated from Linux, so line endings are Unix. Should we convert it to windows file endings?

Do you want to make a final check with SimulationX?

from modelica_devicedrivers.

• I do not care about the line endings.
• Should the copyright be adapted to 2015?
• Is the help folder location correct or should it rather be in Resources?

from modelica_devicedrivers.

Not sure what to do with the copyright notice. I'm not at DLR any more, neither are you. Not sure how this should be handled.

The help folder is the standard folder where Dymola puts generated documentation. From my side that folder is not so important. It was a convention for libraries that were shipped with Dymola to have such a folder. Is there a standardized location for the help folder and should we have such a thing?

from modelica_devicedrivers.

OK, leave that copyright as it is now.

Modelica_DeviceDrivers-1.3-build.2.zip did not contain the help folder. So I was wondering. I do not mind after all.

from modelica_devicedrivers.

All non-modelica code is supposed to be placed under Resources. So help should be Resources/help. I've told DS so ages ago but doubt they have updated their tool yet. It's only been 6 years or so ;-)

from modelica_devicedrivers.

But is it needed after all?

from modelica_devicedrivers.

help/? No. It's just a generated HTML documentation. Some people prefer to have it, though I normally look at the documentation from inside the tool, never with a webbrowser.

from modelica_devicedrivers.

I deleted it. Makes the compressed archives a bit smaller.

from modelica_devicedrivers.

Can I change the status from Draft to Release?

from modelica_devicedrivers.

Did you run the tests?

from modelica_devicedrivers.

No. Did run some of the tests (I don't have all the required hardware) for the alpha release. Also I currently have no free license to check out. I just hope that things are working as they did before.

from modelica_devicedrivers.

OK.

Things TODO.

1. Make the Release then
2. Edit the Readme.md
3. Write some short notice for the Modelica newsletter before Sep. 4 and send it to @mtiller.
4. Close this issue.

from modelica_devicedrivers.

Don't send me the notice. You need to go to http://newsletter.modelica.org and submit the article through the web. If you need a login, send an email to [email protected].

from modelica_devicedrivers.

Can we please get it finished by today? 🙏

from modelica_devicedrivers.

Working on it now. Sorry for the last minute actions. I had a high priority date this week, but now that's done and I'm much more relaxed :-).

I updated the Readme.md with the new release information. Can I state that all non-clocked parts work now with SimulationX?

from modelica_devicedrivers.

Well with userBufferSize all non-clocked parts are working, but autoBufferSize only works for external solvers CVode and Fixed Step solver and fails for BDF and MEBDF solvers. See #54 (comment). I think this might be worth to mention.

from modelica_devicedrivers.

You mean the newsletter, I guess?

from modelica_devicedrivers.

Particularly for the project description (see section "Current release") but I would also mention the improved support of SimulationX in the newsletter.

@tbeu There is now a proposal for the newsletter item in which I added you as "item contributor". That way you should be able to edit that entry, too. Maybe you can have a look whether it looks fine for you and edit it if you find any issues.

from modelica_devicedrivers.

Saw it, but cannot edit. Can you please edit

• Many more small fixes, particularly for improved Modelica and tool compatibility.

Contributor is fine though.

from modelica_devicedrivers.

Ok, changed it.

So we finally have a new release now and I can close that issue :-).

from modelica_devicedrivers.

✅🎆🍻1️⃣4️⃣0️⃣🆒

from modelica_devicedrivers.