docs: Add DSP-META to docs

[BalduinLandolt]

No description provided.

[jnussbaum]

Usually, we don't bump the submodules to the latest state. Rather, we wait until a deployment happens, and then we bump the submodules to the state of the version that was deployed. That means, the submodules should always be at the state defined in release.mk.

When you're on it, would you like to fix the wrong version of DSP-TOOLS in release.mk? It should be "v9.0.2", which is the latest clean release. (I think I once added the commit hash to make an informal after-deployment of the docs).

[BalduinLandolt]

Usually, we don't bump the submodules to the latest state. Rather, we wait until a deployment happens, and then we bump the submodules to the state of the version that was deployed. That means, the submodules should always be at the state defined in release.mk.

When you're on it, would you like to fix the wrong version of DSP-TOOLS in release.mk? It should be "v9.0.2", which is the latest clean release. (I think I once added the commit hash to make an informal after-deployment of the docs).

Good thing you made me double-check! It was actually broken due to a wrong meta tag...

And, yes, I know that we normally don't update the submodules until the deployment, but I figured it doesn't matter as long as the docs don't get deployed. Should I revert?

[jnussbaum]

Usually, we don't bump the submodules to the latest state. Rather, we wait until a deployment happens, and then we bump the submodules to the state of the version that was deployed. That means, the submodules should always be at the state defined in release.mk.
When you're on it, would you like to fix the wrong version of DSP-TOOLS in release.mk? It should be "v9.0.2", which is the latest clean release. (I think I once added the commit hash to make an informal after-deployment of the docs).

Good thing you made me double-check! It was actually broken due to a wrong meta tag...

And, yes, I know that we normally don't update the submodules until the deployment, but I figured it doesn't matter as long as the docs don't get deployed. Should I revert?

No, you can leave it. Now, the submodules are in sync with release.mk, so that's okay.

[BalduinLandolt]

Usually, we don't bump the submodules to the latest state. Rather, we wait until a deployment happens, and then we bump the submodules to the state of the version that was deployed. That means, the submodules should always be at the state defined in release.mk.
When you're on it, would you like to fix the wrong version of DSP-TOOLS in release.mk? It should be "v9.0.2", which is the latest clean release. (I think I once added the commit hash to make an informal after-deployment of the docs).

Good thing you made me double-check! It was actually broken due to a wrong meta tag...
And, yes, I know that we normally don't update the submodules until the deployment, but I figured it doesn't matter as long as the docs don't get deployed. Should I revert?

No, you can leave it. Now, the submodules are in sync with release.mk, so that's okay.

But now the tests fail 🙈
The last released version of meta does not have the mkdocs setup yet...

[mpro7]

This is a unfortunate setup :( but nothing related to this repo...

[BalduinLandolt]

yes, I thought the same