Christoph Ruegg

Do you see an exception or stack trace?

Looks like .Signed packages are no longer properly depending on the .Signed variants of their dependencies since 5.0.0-alpha08. This is certainly not intended, I'll have a look.

Do you work with the generic base types (`Matrix`, `Vector`) or with the explicit types in the sub-namespaces? It seems to me we should rather add conversion on the base...

Maybe related to #3879

I've dropped the prerelease marker for the v0.3.0 release, so it is no longer technically a prerelease (although by convention 0.x versions are still exempt from some strict semantic versioning...

I'm not aware anyone us currently working on this already, but figures like cubes and cones would indeed fit perfectly into the scope of this project.

Yes, this needs to be documented like in [Numerics](https://numerics.mathdotnet.com/Build.html#Creating-a-Release) - but up to date. In Numerics, creating a release is essentially: - Add release notes entry in RELEASENOTES.md. - Run...

I finally upgraded the build framework and release a new beta. Before we do a proper release (without beta prerelease tag) we should have a look at how to package...

It seems I've missed to notice unexpected package references in the resulting NuGet package - tracked in #161.

@li0nsar3c00l are you referring to the fact that there are two paket.references files instead of just one? Or that there is a paket.references file in the first place? Or something...