Skip to content

Labels

Labels

  • Issue is accepted, but is not ready to be worked on or not in current sprint.
  • Issue is accepted, but a milestone has yet to be added for the issue.
  • Insufficient information for issue or PR, issue may be closed if no response from user.
  • Issue is accepted, milestone added and are ready to be worked on.
  • A user or team member has started working on the issue.
  • Code has been added, and is available for review as a pull request.
  • Code has been added to the repository, and has been reviewed by a team member.
  • The issue has been resolved in an upstream project meaning this issue can also be resolved.
  • The issue has been resolved, and released to the public for consumption.
  • Things that typically go to Test-Kitchen - once completed, IN REGRESSION TEST SUITE label added.
  • Manual tests has not been added for issue - once completed, IN MANUAL TEST SUITE label added.
  • Issues that handles API changes, not necessarily visible to end users.
  • Issues that represent refactoring code for maintainability.
  • The pull request opened was not accepted, didn't follow the procedures, or was missing information.
  • The issue or pull request is not fixable without a change in a upstream/external library.
  • The issue will introduce backwards incompatible changes.
  • Issues where something has happened which was not expected or intended.
  • Issues for changes to the build system, without functional changes needed to the project.
  • Issues that will only be accepted from the core Chocolatey Team.
  • Bug reported or feature requested by a licensed customer of Chocolatey.
  • If a dependency or bundled binaries are added, removed or updated.
  • Features or functionality that is being deprecated in favor of removing or replacing them in future.
  • Issues for changes that only need to change documentation.
  • Issues that are duplicates of other issues.
  • Issues that introduce new functionality to the project, or enhances/updates existing functionality.
  • Issues opened during hacktoberfest.
  • Pull Requests opened during hacktoberfest, and has been accepted by a team member.
  • This issue has a related issue that would need to be addressed before this issue can be closed.
  • These are things that are documented to test as part of a release.