-
Notifications
You must be signed in to change notification settings - Fork 458
Closed as not planned
Labels
locked[bot] locked due to inactivity[bot] locked due to inactivitysource::anacondacreated by members of Anaconda, Inc.created by members of Anaconda, Inc.stale[bot] marked as stale due to inactivity[bot] marked as stale due to inactivitystale::closed[bot] closed after being marked as stale[bot] closed after being marked as staletype::featurerequest for a new feature or capabilityrequest for a new feature or capability
Description
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
- 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 - Add CEP 5 : Adopting Grayskull as the defacto conda recipe generator ceps#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?
Metadata
Metadata
Assignees
Labels
locked[bot] locked due to inactivity[bot] locked due to inactivitysource::anacondacreated by members of Anaconda, Inc.created by members of Anaconda, Inc.stale[bot] marked as stale due to inactivity[bot] marked as stale due to inactivitystale::closed[bot] closed after being marked as stale[bot] closed after being marked as staletype::featurerequest for a new feature or capabilityrequest for a new feature or capability
Type
Projects
Status
🏁 Done