cschol

So the plugin developer submits a PR for their updated manifest, which we will merge if it's approved? Do I still update the repo to the correct SHA? It would...

OK. That makes sense and I agree has worked well. I don't see any reason why not for the v1 branch.

Here are a few thoughts on the overall migration process: - The Library Team is only migrating **open-source** plugins. Correct? - Every open-source plugin **must** have an (open/closed) **issue in...

Thank you! Project board for `v1` migration is available at: https://github.com/VCVRack/library/projects/1 If a plugin is available for `v1` should we begin the migration now or hold off for a while...

Yeah, I was referring to early migrated `v1` plugins. I'll keep the issues `v0.6` vs `v1` straight in the project boards. You only need to process issues in state "Plugin...

As I am starting to integrate `v1` plugins that have been updated, I will close the issue after moving to the **Needs Build Update** state. I assume there will be...

@squinkylabs Exactly. Use the same, existing issue for both (for right now).

@AndrewBelt When you start to build plugins for `v1`, can you check your build process for plugins that build `libsamplerate` as a dependency, e.g. Fundamental? I have trouble crosscompiling it...

The `libsamplerate` build dependency is not new for the Fundamental plugin, right? Are you building the plugins on their respective platforms (e.g. on Windows) or cross-compiling for the plugin manager...

I took a look at the crosscompilation. Adding the "--host" option and a reference to mingw32's `ar` to `configure` in the Fundamental `Makefile` will allow successful cross-compilation of Fundamental on...