We've always wanted a way to have pyctdev update conda-forge for us. That's a reasonably big job because it involves integrating couple of systems (at least, as far as I know). However, Jim's pointed out that it should at least be straightforward to be alerted to problems. E.g. a cron job running on travis could fail if the latest version on conda-forge isn't what's available on pyviz, could fail if the dependencies are different (and report the diff), etc.
We've always wanted a way to have pyctdev update conda-forge for us. That's a reasonably big job because it involves integrating couple of systems (at least, as far as I know). However, Jim's pointed out that it should at least be straightforward to be alerted to problems. E.g. a cron job running on travis could fail if the latest version on conda-forge isn't what's available on pyviz, could fail if the dependencies are different (and report the diff), etc.