Release to conda-forge and defaults simultaneously

[jlstevens]

For 1.10 the plan is to to update the recipe on conda-forge and then immediately get that recipe onto anaconda defaults channel so conda install holoviews works without specifying a channel. The goal is to move away from using the ioam channel and maybe use the holoviews channels for 'nightlies' (actually automated packages for PRs merged to master).

[ceball]

Is the plan that 'latest master' conda packages for param (+gui toolkits) would also be uploaded to the holoviews channel?

[jlstevens]

I'm not sure how much of that is 'holoviews', so maybe we should make a general 'pyviz' channel?

[jbednar]

A pyviz channel seems like an excellent idea.

[jbednar]

Instead of a holoviews channel.

[jlstevens]

That would be fine by me..the holoviews channel never really got used.

[ceball]

Yes, fine with me. I asked because I'm keen for there to be as few channels as possible...ideally just one even...

[jlstevens]

I've registered pyviz on anaconda.org so we can start using that...

[jakirkham]

Would there be any interest in doing dev releases on conda-forge? Just noticed 1.10.0a1 got tagged so figured I'd ask. ;)

[jlstevens]

@jakirkham I'm not against this idea, especially if it can be automated.

If it can't be automated, then it means these releases are more work to do which means they are more likely to be infrequent (something we are currently trying to get away from!)

[jlstevens]

Or alternatively, if someone else is willing to update conda-forge for dev releases. :-)

[jakirkham]

There's been some work on an autoupdate bot. It's very new and docs are scarce. That said, most maintainers don't need to do anything with it per se. However it could learn a few things like how to update the dependencies or other recipe metadata. Though it's pretty good for being around a little over 1wk. :)

Was asking as this particular dev release was interesting to me. That said, can't promise that I'll always be able to update all dev releases. Hope you understand. :)

[jlstevens]

Looks like the autoupdate bot will ignore alphas: conda-forge/holoviews-feedstock#25

Shame as dev builds from -c conda-forge/label/dev would have been nice!

[jakirkham]

Yeah I agree.

It's a little complicated as handling every projects' dev releases likely comes with a significant burden resource-wise and maintenance-wise. OTOH it's a really nice service to provide to developers and users. Not sure the right way to untangle it ATM, but did leave a note along these lines.

[jlstevens]

Dev builds are now configured on conda-forge for holoviews:

conda install -c conda-forge/label/dev holoviews

This is just a reminder for myself to update the source correctly in meta.yaml on the feedstock master when 1.10 is released.

[philippjfr]

I've closed the other conda-forge related issue and would like to close this one too. @jlstevens If you want to record anything here, I'd prefer opening a packaging meta-issue to describe anything we need to remember during our migration to pyct.

[philippjfr]

On second thought, please do open such a issue if you think it's a good idea but this issue seems to be specifically about 1.10 and mentions long outdated plans about a holoviews channel so I'm closing as I'm cleaning up in anticipation for a 1.11 release and reassigning issues to the 1.11.x release series.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.