Attendees

• Eric, Greg, TomG, TomF, Elaine, Scooter, Conrad

Agenda

• Action items
• Chimera
  • After 1.13.1 release
    • Fedora 29 lib problems
• ChimeraX
  • RBVI bundles on toolshed
    • Change build process to trim down list of bundles in standard release while still testing toolshed-only bundles
  • Stable APIs, #922
  • Documentation strategy
  • After 0.8 release
    • Update to Python 3.7
    • Update prereqs
    • Update Qt/PyQt
  • 1.0 features (roadmap)

Discussion

• After 1.13.1 release
  • Fedora 29 library problems are fixed in daily build
    • Tested both with Fedora 29 and older version
    • Feedback positive
  • Next release?
    • No further bug reports
    • Leave it for now, unless lots of reports come in again
• ChimeraX
  • Putting RBVI bundles on toolshed
    • Want separate run-time vs build-time dependencies in bundle_info.xml
  • Stable APIs
    • See action items
  • After 0.8 release
    • Update to Python 3.7
      • OpenMM should have a generic release for 3.7 now
      • Greg will find out whether OpenMM-CUDA == "OpenMM-generic + CUDA"
      • Need strategy on how to support available hardware/software CUDA/OpenCL
      • Initially, just use generic version so we can get to Python 3.7
    • Update prereqs
      • Conrad is working on it
      • numpy/scipy depend on Python version
      • New Cython needs to be tested for Windows
    • Update Qt/PyQt
      • Currently using 5.9
      • Last 5.11 test blew up
      • Greg will build 5.12 PyQt dev release for internal test
  • Move to github
    • Move to private RBVI github project
      • Easier to share with collaborators with github admin tools
      • "pull requests" should simplify enhancement/fix submission
      • will not happen that soon

Action Items

• Conrad will look at "git flow" for common practice
  • ​https://datasift.github.io/gitflow/IntroducingGitFlow.html
  • Conrad will make "git flow" ticket for 0.9 and master branch
• Conrad will look at Sphinx for adding link for "all methods even from base classes"
  • :inherited-methods can be used judiciously. For example, the AtomicStructure class should use it because its base classes are not intended for public consumption, but StructureSequence might not because its base class Sequence can be used independently.
• Greg will implement documentation virtual overlay symlink target