6 | | > What if we simply require that new, non-security updates for plugins moving forward must use tags instead of trunk for updates? Not sure how easy it is to do so, but there could be a git commit hook on trunk that looks to see if version changes in the readme.txt in trunk and rejects the commit with a "Please use tags for new releases. For more information see: (url)" as an idea |
| 6 | > What if we simply require that new, non-security updates for plugins moving forward must use tags instead of trunk for updates? |
| 7 | |
| 8 | Not sure how easy it is to do so, but there could be a git commit hook on trunk that looks to see if version changes in the readme.txt in trunk and rejects the commit with a "Please use tags for new releases. For more information see: (url)" as an idea |