library
library copied to clipboard
Library repo maintenance
@AndrewBelt
I created a project board for library maintenance (right now for v0.6, later for v1.0):
https://github.com/VCVRack/library/projects/2
If an existing issue assigned to this project gets reopened, it gets automatically assigned to the "Plugin integration in repo" column. Once I integrate it, I will move it to the "Plugin build update" column. When you update the build and close the issue, it will automatically move it to the "Plugin available for v0.6" column.
Only issues labelled "plugin" are assigned to this board.
Issues for new plugins should be assigned to the "v0.6 library maintenance" project. Then they will automatically assigned to the "Plugin integration in repo" column.
This should make it more obvious for the Library team, which plugins need updates. I sometimes miss them in the normal issue list and they sit there for a while.
Oh yeah, I forgot about project hooks/triggers. Those will make things a lot easier.
Proposal to remove the following plugins from the library (master branch):
- Autodafe Blank Panels (I have confirmed with the author that they are obsolete)
- dekstop (The plugin was actually never available in the plugin manager for any version of Rack)
Removing old plugins is fine with me.
I am trying to get to portable review capabilities with my Mac.
Two issues I found on a Mac (non-case sensitive file system...):
manifestscontainsMental.json(valid) andmental.json(old, obsolete). I would like to removemental.json.repos/Quadraphonicsrepo has two folders with the same name and different capitalization. Since it has not been updated, can we remove it fromrepos? We can readd it once it has been ported tov1. I filed an issue with the plugin author, but it is unlikely to be fixed anytime soon.
- Yes, remove
mental.json. - Sure. We don't have to strictly follow the rule of "every open-source build needs a submodule in
repos/.
Cool. Thanks. I will make those updates.