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

followup with examples for the new deprecation policy #6324

Open
5 tasks
RonnyPfannschmidt opened this issue Dec 7, 2019 · 5 comments
Open
5 tasks

followup with examples for the new deprecation policy #6324

RonnyPfannschmidt opened this issue Dec 7, 2019 · 5 comments
Assignees
Labels
type: docs documentation improvement, missing or needing clarification

Comments

@RonnyPfannschmidt
Copy link
Member

RonnyPfannschmidt commented Dec 7, 2019

#6298 introduces a new deprecation policy and the potential for breaking changes in different ways

in order to help with future expectations this needs to be followed up with some examples for the documentation process before we implement one of those in actuality

#6293 is an example of such changes
similar holds true to various other plans/ideas for bringing the fixture system and node structures forward

while we are at it we should also ensure we have transitional details tracked in both issues and projects for more details

@RonnyPfannschmidt RonnyPfannschmidt self-assigned this Dec 7, 2019
@Zac-HD Zac-HD added the type: docs documentation improvement, missing or needing clarification label Dec 8, 2019
@nicoddemus nicoddemus added this to the 6.0 milestone Dec 8, 2019
@graingert graingert changed the title folllowup with examples for the new deprecation policy followup with examples for the new deprecation policy Dec 21, 2019
@shivankgtm
Copy link

Anyone working on it? If not will it be fine to handle as a first contribution on pytest? or I should choose something less critical?

@nicoddemus
Copy link
Member

Hi @shivank98,

This is kind of a tricky issue because requires a deep knowledge of the internals plus the effects of future refactorings will have on the existing code base.

I suggest you take a look at issues marked with the easy label instead for a first contribution. 👍

@nicoddemus
Copy link
Member

@RonnyPfannschmidt you still want to tackle this for 6.0?

@RonnyPfannschmidt RonnyPfannschmidt modified the milestones: 6.0, 6.1 Jun 16, 2020
@nicoddemus
Copy link
Member

@RonnyPfannschmidt gentle ping. Do you think you will be able to tackle this soon?

@RonnyPfannschmidt
Copy link
Member Author

I'm going to try and get some time on the weekend for this

@nicoddemus nicoddemus mentioned this issue Sep 2, 2020
@nicoddemus nicoddemus removed this from the 6.1 milestone Sep 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: docs documentation improvement, missing or needing clarification
Projects
None yet
Development

No branches or pull requests

4 participants