Publish dev nbsite to a new tooling_dev channel

[maximlt]

I would like to be able to build hvPlot's docs without any HoloViz dev release but with a dev release of nbsite. This is currently not possible (or at least not easily). With this PR nbsite will get additionally published to tooling_dev (dev releases) and tooling (main releases) channels.

[hoxbro]

I don't know if we need two channels for this, as it is an internal tool on our channel.

But I don't have a strong opinion either way—other than if we want two channels, we should apply my suggested change.

[maximlt]

I don't know if we need two channels for this, as it is an internal tool on our channel.

Do you mean 1 channel instead? Just tooling_dev? Might be fine yes.

[hoxbro]

Do you mean 1 channel instead? Just tooling_dev? Might be fine yes.

Yes, maybe just tooling to keep it short.

[maximlt]

Do you mean 1 channel instead? Just tooling_dev? Might be fine yes.

Yes, maybe just tooling to keep it short.

Hmm sometimes I may want pyviz/label/dev but not a dev version of nbsite.

[hoxbro]

Hmm sometimes I may want pyviz/label/dev but not a dev version of nbsite.

Your suggested changes won't solve that either, right? As nbsite is still upload to dev.

[maximlt]

Ah yes true 🤦 In which case I'd suggest no longer publishing nbsite to dev and main.

[hoxbro]

I'm not a fan of that. Wouldn't it be easy enough to pin nbsite in that case?

[maximlt]

I'm not a fan of that. Wouldn't it be easy enough to pin nbsite in that case?

It depends on what you want to achieve. Pinning is imo an okay solution short term but is annoying long term. I've had a quick look at these repos and saw that most of them build the docs with the pyviz/label/dev channel, I'm not sure that's the right thing to do? Perhaps this channel was set up at some point to get a dev release of nbsite and then forgotten, I'm not sure. I also noticed nbsite is pinned to 0.8.4 on Param's doc build.

• HoloViews: pyviz/label/dev
• GeoViews: pyviz/label/dev
• Panel: pyviz/label/dev
• Datashader: pyviz/label/dev
• hvPlot: conda-forge with dev install of nbsite from pip
• Lumen: pyviz/label/dev
• Param: nbsite ==0.8.4" from pip

[hoxbro]

Pinning is imo an okay solution short term but is annoying long term

But we control the whole chain, so we can always push a fix if we need it.

build the docs with the pyviz/label/dev channel, I'm not sure that's the right thing to do?

I feel like we have this talk every six months or so 🙃

In my opinion, it is not a black-and-white case. Sometimes, you need to have the latest dev release for one of our package to be able to publish the documentation. Sometimes, it doesn't matter if it is dev version or full release, and sometimes, we should use the full release.

I don't think we can make a definite rule, as it will almost always depend on the case.

Perhaps this channel was set up at some point to get a dev release of nbsite and then forgotten

This only argues for a tooling-only channel, not the removal of nbsite for the existing channels, IMO.

[maximlt]

@hoxbro are you okay with a tooling_dev channel only?