Kai Jaeger

When a package `Foo` is opened that has dependencies that themselves depend on `Foo` then things go awry: the principal package is not being taken into account when the build...

The current syntax works but is quite complex. Adding an optional flag `-bump=` would simplify matters: ``` -bump=major -bump=minor -bump=patch ``` should all be handled.

Currently creating an API automatically requires calling a function of the `BuildHelpers` package. It is possible to integrate this into `BuildPackage`. `BuildHelpers.CreateAPI` handles all scenarios: * Niladic, monadic, dyadic and...

The current implementation works fine with .NET 3.1 (formerly known as .NET Core). It causes for reasons that probably even Microsoft cannot explain a VALUE ERROR after .NET got upgraded...

Currently we have just one assets folder. There are good reasons to have platform-dependent asset folders. For example, Conga, when it's a Tatin packages, could bring just the DLLs that...

The config parameter `api` must be either the name of a class or a namespace, hosting the API of a package. `BuildPackage` does not check this, allowing it to be...

It should allow a review as well as the assignment of 1-5 stars.

With `InstallPackages` this might be the right thing to do, but it is less clear with `LoadPackages`. Shouldn't Tatin load everything that did not cause an error and report problems...

`GetAllPackages` should be called only by the compile-index process. Everything else that is calling it should use the pre-compiled list instead because that's faster.

Tatin should allow a user to register for a newsletter, announcing new versions, discussing plans, and road maps and maybe even announce newly published (deleted?!) packages.