NuGet update strategy / frequency

[whugemann]

I have just seen that Dirk reacted to #1856 and elimited the write protection of PointD. How long will it take until the NuGet packages get updated? I guess that Dirk doesn't update them in case of every minor change (?). Is there a general schedule / strategy for that?

Deplorably, there seems to be no mechanism that informs you about such updates in Visual Studio, i.e. you have to initiate the update yourself via the package manager and see whether there's a new update or not. (I'm a littly shy of compiling Magick.NET myself.)

@ Dirk: I don't want to rush you. For the moment I'm happily working on another Magick.NET project.

[dlemstra]

I have already answered this question a couple times and the answer is that there is no real update strategy/frequency. It happens when it happens. Most of the time there will be a new release every month but there are some changes now in the ImageMagick project that are delaying the release because we want to make sure they are done correctly. We are now in the final part of these changes so it will probably happen soon.

You can keep track of this by putting a watch on the releases:

p.s. There is no need to use my name because I am the only person working on this project 😉

[whugemann]

Thanks for this explaination. I really tried to google it, but wasn't successful. I still haven't got used to Github's UI ...
In regard to update strategy, you might consider rewording the readme text at https://www.nuget.org/packages/Magick.NET.Core (and alike). I searched at least this forum before asking and didn't find an answer.

[dlemstra]

It is probably well hidden in the responses 😁I don't think I want to add this to the documentation, it's not very common to communicate an release frequency. It happens when it happens.