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

mark latest python 3.8 on osx-64 as broken #267

Merged
merged 1 commit into from Jun 7, 2021
Merged

Conversation

isuruf
Copy link
Member

@isuruf isuruf commented Jun 7, 2021

Guidelines for marking packages as broken:

  • We prefer to patch the repo data (see here)
    instead of marking packages as broken. This alternative workflow makes environments more reproducible.
  • Packages with requirements/metadata that are too strict but otherwise work are
    not technically broken and should not be marked as such.
  • Packages with missing metadata can be marked as broken on a temporary basis
    but should be patched in the repo data and be marked unbroken later.
  • In some cases where the number of users of a package is small or it is used by
    the maintainers only, we can allow packages to be marked broken more liberally.
  • We (conda-forge/core) try to make a decision on these requests within 24 hours.

Checklist:

  • Make sure your package is in the right spot (broken/* for adding the
    broken label, not_broken/* for removing the broken label, or token_reset/*
    for token resets)
  • Added a description of the problem with the package in the PR description.
  • Added links to any relevant issues/PRs in the PR description.
  • Pinged the team for the package for their input.

See conda-forge/python-feedstock#464

cc @conda-forge/python

@isuruf isuruf requested a review from a team as a code owner June 7, 2021 18:28
@isuruf
Copy link
Member Author

isuruf commented Jun 7, 2021

@conda-forge/core, this is ready.

@ocefpaf ocefpaf merged commit 5ebe089 into conda-forge:master Jun 7, 2021
@isuruf isuruf deleted the 3.8 branch June 7, 2021 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants