-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Comments
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? |
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 |
@RonnyPfannschmidt you still want to tackle this for 6.0? |
@RonnyPfannschmidt gentle ping. Do you think you will be able to tackle this soon? |
I'm going to try and get some time on the weekend for this |
#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
The text was updated successfully, but these errors were encountered: