Mark conda-build skeleton as "Pending deprecation"

[travishathaway]

What is the idea?

We eventually want to remove conda-skeleton from conda-build and instead have Grayskull be the de facto way for generating new recipes from existing packages.

What should happen?

To help us achieve this goal, one of the first steps is to mark this feature as "pending deprecation" according to conda's official deprecation policy outlined in CEP-9.

Tasks

• [x] When conda-build users run conda skeleton, they need to be presented with a "pending deprecation" warning that will link them to the Grayskull project
• [ ] https://github.com/conda-incubator/ceps/pull/17 needs a vote
• [ ] Determine when this will receive the official "deprecation" status.
  • According to CEP-9, the "pending deprecation" status must last at least two regular releases. Do we want even more time for this?

[mbargull]

xref: https://github.com/conda-incubator/grayskull/issues/422 It would be helpful to have most of the non-PyPI parts added to Grayskull before or during the deprecation phase and ideally before its final removal, of course.

[github-actions[bot]]

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   • What OS and version you reproduced the issue on
   • What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!