Transitioning to the conf.d enabling approach about jupyterlab-feedstock HOT 9 CLOSED

👍

from jupyterlab-feedstock.

I propose that we start the transition by deleting the unlink scripts with the next version of JupyterLab, and wait at least 6 months (i.e., a year after notebook 5.3 was released) for people to move to these newer versions of JupyterLab and the notebook before deleting the link scripts.

from jupyterlab-feedstock.

Sounds good to me

from jupyterlab-feedstock.

I propose that we start the transition by deleting the unlink scripts with the next version of JupyterLab, and wait at least 6 months (i.e., a year after notebook 5.3 was released) for people to move to these newer versions of JupyterLab and the notebook before deleting the link scripts.

Let's try to remember to delete the unlink scripts for the 0.35 release.

from jupyterlab-feedstock.

I deleted the unlink scripts in #144 (jlab 0.35). I think we probably can delete the link scripts and move to noarch in the next version, which will probably be maybe 10 months after notebook 5.3 was released?

from jupyterlab-feedstock.

Sounds good, thanks!

from jupyterlab-feedstock.

Oops, we should have done this for 1.0. I suppose we can do it for 1.1, though. I hesitate to make this change in a patch release, though.

from jupyterlab-feedstock.

I'm doing a trial run of switching to the noarch package in the new prerelease branch.

from jupyterlab-feedstock.

We can easily do this switch if we:

• copy the prerelease branch recipe meta.yaml to master
• delete the scripts in the master recipe
• rerender the recipe

(Don't copy the prerelease branch conda_build_config.yaml file)

from jupyterlab-feedstock.