Skip to content

[Community] The Guidelines for Issues and Features #4578

@winlinvip

Description

@winlinvip

Now that AI is diligently helping manage the issues, we have to set a few guidelines for everyone to uphold, so that we can avoid any unnecessary hindrances and handle issues and features with more ease.

  1. Every issue must have a clear and comprehensive description for the AI to reproduce and resolve.

    1. It can be a bug report with detailed call stacks, a root cause analysis, a bug report with straightforward reproduction steps, or a feature request with detailed background information.
    2. If you have a general issue report without detailed information, you should go to Discord and discuss it with others. You should never submit an issue until you have a clear description.
    3. If you submit an issue with a vague description, and the AI cannot reproduce or fix it, it will be closed as "no plan" or "cannot fix."
  2. Every issue will not stay open without any progress, unless it's a devoted feature.

    1. A clear issue will be reproduced and fixed, or closed if it cannot be fixed or there is no plan to do so.
    2. We won't keep an issue open and update it without any useful information, because it doesn't make sense.
    3. Nobody will jump into issues and try to help you with a vague issue; it just never happens.
  3. The most crucial step is to reproduce a bug in a straightforward manner.

    1. If you cannot reproduce a bug, then it cannot be fixed by anyone.
    2. Consistently encountering bugs that are difficult to reproduce suggests that your architecture needs refinement.
    3. Look for alternative solutions if you encounter difficulties.

Metadata

Metadata

Assignees

No one assigned

    Labels

    EnglishNativeThis issue is conveyed exclusively in English.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions