​​2018-07-17 conda-forge meeting
​​Pinned Items
​​
​​New items
  • ​​Update on current status
  • ​​Number of packages left to syntax migrate
  • ​​Number of packages needing re-compile
  • ​​Total number ready
  • ​​Number ready in the first layer
  • ​​Build number increase by N for new things at build time non static
  • ​​determine build number with conda render clobber file
  • ​​Decide on migration order [Outcome: make super graph of py37 + compilers (run with one walker), drop 3.5 when 3.7 starts]
  • ​​py37
  • ​​compilers
  • ​​remaining compiler syntax
  • ​​Decide on resource strat [Outcome: do everything online]
  • ​​Offline (without CIs)
  • ​​Online (with CI)
  • ​​Decide on channel strat [Outcome: new label for new compilers, run two labels]
  • ​​upload re-compiled packages to new label and continue pushing to current label
  • ​​upload re-compiled packages to current label, push updates to current era compilers to different branch
  • ​​Establish next steps/action items/gh issues
  • ​​Decide on a policy for when maintainers stop maintaining
  • ​​Related to 2k-ish pending bot PRs…
  • ​​Sharing passwords (to start off the meeting next time)
​​
​​Existing Items
  • ​​Moving compiler syntax
  • ​​Decide on strat
  • ​​Finding a good solution to sharing passwords among core
  • ​​Michael Sarahan to document and give demo on how to transition old recipes to new style
  • ​​5/1: Will wait for more people on the dev call before Mike talks about this
  • ​​Build packages on C3I and upload to conda-forge
  • ​​Make is missing from the base image for PowerPC internal to Anaconda. Fun times!
  • ​​Mike is open to other people helping with this.  If interested, reach out!  Helping means trying recipes, debugging any issues, and resolving any merge conflicts that have happened since Mike pulled them in last.  Moving target.
  • ​​Packages that have been built https://anaconda.org/cf-cb3 - these may need more work regarding versions.  The graph was computed with the versions, but probably should have ignored them.  When a pin is older than a newer recipe, the upstream recipe gets missed as a real dependency because of the version mismatch.
  • ​​switch to cb3
  • ​​what kind of things are going to break when we change compilers?
  • ​​(​@Jonathan H​ had a great response that I hope he’ll clarify here:) tl;dr C++ ABI
  • ​​Making the agenda and notes public again.
  • ​​John will see if we can make dropbox paper readable by the world
  • ​​other options are to just post the notes somewhere public after the meeting
  • ​​conda-forge blog
​​