Deprecation Julep
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 75
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
We need an explicit policy for how deprecations will be handled post-1.0. Some options are:
1. Allow them in minor releases, removed next minor release
2. Allow them in minor releases, removed next major release
3. Allowed only in major release, removed next minor release
- Could be added in minor releases, but hidden have `--depwarn=no` by default.
We can use this issue for preliminary discussion until the appropriate Julep is written.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the three deprecation-policy options and the existing discussion in this issue. Determine whether the policy has been settled; done would be a clear decision recorded in an appropriate Julep, rather than an implementation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100