Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate old npm repos #151

Closed
jasongrout opened this issue Jun 23, 2016 · 9 comments
Closed

Deprecate old npm repos #151

jasongrout opened this issue Jun 23, 2016 · 9 comments
Assignees
Labels
maintenance status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. tag:Build System
Milestone

Comments

@jasongrout
Copy link
Contributor

We should deprecate these on npm and put a note in the package.json description that they have been superseded by the jupyterlab package:

  • jupyter-js-notebook
  • jupyter-js-docmanager
  • jupyter-js-domutils
  • jupyter-js-terminal
  • jupyter-js-filebrowser
  • jupyter-js-ui
  • jupyter-js-plugins

We should also note in the github repos that the repos have been superseded by the jupyterlab repo. We should probably move the repos to some jupyter-attic github org.

@jasongrout
Copy link
Contributor Author

I think this covers all of the bases:

  • move the repo to the jupyter-attic org
  • Update each one-line repo description on github to say "Deprecated"
  • Update the readme files to point to the new repo
  • update the package.json description so the deprecation shows up in npm
  • update the package.json repo to point to the jupyter-attic location
  • use the npm deprecation command to officially deprecate the repo

@jasongrout
Copy link
Contributor Author

This is done!

@jasongrout
Copy link
Contributor Author

Nope, not done! The npm package needs to be deprecated...

@jasongrout jasongrout reopened this Jul 22, 2016
@jasongrout jasongrout self-assigned this Jul 22, 2016
@ellisonbg
Copy link
Contributor

@jasongrout is this still relevant - did you finish it?

@ellisonbg ellisonbg added this to the 1.0 milestone Aug 25, 2016
@jasongrout
Copy link
Contributor Author

Not yet. Probably still relevant - just need some time for the woodcutting, as @SylvainCorlay would say.

@jasongrout
Copy link
Contributor Author

(some of it is done...)

@ellisonbg
Copy link
Contributor

ping...

@ellisonbg
Copy link
Contributor

still relevant...

@blink1073
Copy link
Member

I deprecated all of the listed packages.

@lock lock bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Aug 8, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
maintenance status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. tag:Build System
Projects
None yet
Development

No branches or pull requests

3 participants