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

DOC: Instruct to run git bisect when triaging a regression report #58813

Merged

Conversation

Aloqeely
Copy link
Member

@rhshadrach (ref #55311)
The issue suggested to include the results of a git bisect when triaging regressions.

As for step 7, it says "what labels and milestones should I add" but has no instructions on adding milestones, the only thing I'm aware of is generally regressions are to be fixed as soon as possible so add to the next patch release, if that is not correct then I'll just rename the section.

Another note is that many steps suggest to edit the original post/title but triage permissions aren't sufficient for that, should I delete those?

@Aloqeely Aloqeely requested a review from noatamir as a code owner May 23, 2024 04:37
@mroeschke
Copy link
Member

the only thing I'm aware of is generally regressions are to be fixed as soon as possible so add to the next patch release

Yeah I would say this is generally correct. Any other milestone (major or minor release) are used by some core team members as "issues that would be nice to address by this release", so no need to include that in triage instructions

@mroeschke mroeschke added the Docs label May 23, 2024
@mroeschke mroeschke added this to the 3.0 milestone May 23, 2024
@mroeschke mroeschke merged commit 3b48b17 into pandas-dev:main May 23, 2024
20 checks passed
@mroeschke
Copy link
Member

Thanks @Aloqeely

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants