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

Removals/Deprecations in 0.10 #725

Closed
jrleeman opened this issue Jan 31, 2018 · 4 comments
Closed

Removals/Deprecations in 0.10 #725

jrleeman opened this issue Jan 31, 2018 · 4 comments
Labels
Type: API Change Changes to how existing functionality works
Milestone

Comments

@jrleeman
Copy link
Contributor

Slated for removal in MetPy 0.10:

@jrleeman jrleeman added the Type: API Change Changes to how existing functionality works label Jan 31, 2018
@jrleeman jrleeman added this to the 0.10 milestone Jan 31, 2018
@dopplershift
Copy link
Member

Wait, if we haven't deprecated anything for this version yet, and we've now decided that the length of all future deprecations puts it out to the 0.11 version, will this issue ever have anything?

@jrleeman
Copy link
Contributor Author

jrleeman commented Feb 1, 2018

Unsure, but for consistency's sake there should be a removals/deprecations coupled to each milestone. Keeps us checking it and keeps my CDO from going nuts.

@dopplershift
Copy link
Member

On the flip side, you created an issue with literally no work to be done--this drives my practicality nuts. 😁 😱 If you're going ahead and creating the milestone for these versions, why not document the deprecations in the text of the milestone? I'm not fighting hard for this--just pointing out that your quest for order leads to something that's pretty silly.

@jrleeman
Copy link
Contributor Author

jrleeman commented Feb 1, 2018

I'm sure we can argue semantics here forever :)

  • A process is key a la "The Checklist Manifesto" - release should always consist of the same steps - even if one is a no-op.

  • Milestones are not places to track tasks either.

We can discuss and see what we think here, but those are the arguments in favor of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: API Change Changes to how existing functionality works
Projects
None yet
Development

No branches or pull requests

2 participants