On 03/22/2016 05:53 PM, Dan Wilcox wrote:
Maybe the new development is in a diff branch?
i think there are three options: whenever the deken devs are positive that a version of the deken-plugin should be included in Pd-mainstream, - the deken devs create a Pull Request in the pure-data repository - the deken devs push @millerpuckette, asking to pick the current deken-plugin.tcl (doesn't require switching repos) - there is a separate "pd-deployment" branch in the deken repository, where only "ready to be included" versions of the plugin are found. it's always safe to include the latest version of this branch into Pd.
as for tagging: i'm not sure, mainly because deken consists of two components (the plugin and the cmdline upload-tool). since the plugin has been included into Pd-mainstream, focus has shifted considerable towards the cmdline tool: the last commit to the plugin code was somewhen in summer last year.
having said that, there *is* a v0.1 in the repository, and this tag already contains the last change to the deken-plugin. the problem we are facing is, that there there have been changes in the pure-data repository, not reflected in the deken repository.
IOhannes