2018-11-13 conda-forge meeting

Pinned Items

New items

  • ~~Discussing binary size and stripping options (~~~~-S~~~~,~~ ~~-s~~~~,~~ ~~-0s~~~~)~~

    • Solved. Not worth pursuing and the recommend is to strip after if space is an issue.

Previous items

  • Compiler rebuild status

    • python done for both compiler stacks

    • Qt: try to build on Azure?

  • (DISCUSSED/Postponed) New approach to reducing CI load https://github.com/conda-forge/conda-forge.github.io/issues/647

    • Might be possible to not be totally insecure with work. But nobody is volunteering to do that work right now. :)

    • Pushing PR builds to a staging channel might be a nice UX improvement so you can test anyway.

  • Copying packages to gcc7 label https://github.com/conda-forge/conda-smithy/issues/892

    • MPI metapackage

    • Just wait for new conda 4.6 with strict channel priority, and then add main label to those builds

  • (DISCUSSED/Postponed)Mergify = auto-merge version bump PRs when CIs pass?

    • https://github.com/conda-forge/conda-forge-maintenance/issues/49

    • Worry about bot not detecting dependency changes

    • Definitely opt-in only at first

    • One possibility: only after an approved review (so you can say “merge assuming CIs pass”)

  • Add overlinking error flag by default?