| 1 | = Attendees = |
| 2 | |
| 3 | * Eric, Greg, TomG, TomF, Elaine, Scooter, Conrad |
| 4 | |
| 5 | = Agenda = |
| 6 | * Action items |
| 7 | * Chimera |
| 8 | * After 1.13.1 release |
| 9 | * Fedora 29 lib problems |
| 10 | * ChimeraX |
| 11 | * RBVI bundles on toolshed |
| 12 | - Change build process to trim down list of bundles in standard release while still testing toolshed-only bundles |
| 13 | * Stable APIs, #922 |
| 14 | * Documentation strategy |
| 15 | * After 0.8 release |
| 16 | - Update to Python 3.7 |
| 17 | - Update prereqs |
| 18 | - Update !Qt/PyQt |
| 19 | * 1.0 features (roadmap) |
| 20 | |
| 21 | = Discussion = |
| 22 | * After 1.13.1 release |
| 23 | - Fedora 29 library problems are fixed in daily build |
| 24 | - Tested both with Fedora 29 and older version |
| 25 | - Feedback positive |
| 26 | - Next release? |
| 27 | - No further bug reports |
| 28 | - Leave it for now, unless lots of reports come in again |
| 29 | * ChimeraX |
| 30 | - Putting RBVI bundles on toolshed |
| 31 | - Want separate run-time vs build-time dependencies in bundle_info.xml |
| 32 | * Stable APIs |
| 33 | - See action items |
| 34 | * After 0.8 release |
| 35 | - Update to Python 3.7 |
| 36 | - OpenMM **should** have a generic release for 3.7 now |
| 37 | - Greg will find out whether OpenMM-CUDA == "OpenMM-generic + CUDA" |
| 38 | - Need strategy on how to support available hardware/software CUDA/OpenCL |
| 39 | - Initially, just use generic version so we can get to Python 3.7 |
| 40 | - Update prereqs |
| 41 | - Conrad is working on it |
| 42 | - numpy/scipy depend on Python version |
| 43 | - New Cython needs to be tested for Windows |
| 44 | - Update !Qt/PyQt |
| 45 | - Currently using 5.9 |
| 46 | - Last 5.11 test blew up |
| 47 | - Greg will build 5.12 PyQt dev release for internal test |
| 48 | * Move to github |
| 49 | - Move to private RBVI github project |
| 50 | - Easier to share with collaborators with github admin tools |
| 51 | - "pull requests" should simplify enhancement/fix submission |
| 52 | - will not happen that soon |
| 53 | |
| 54 | = Action Items = |
| 55 | * Conrad will look at "git flow" for common practice |
| 56 | - https://datasift.github.io/gitflow/IntroducingGitFlow.html |
| 57 | - Conrad will make "git flow" ticket for 0.9 and master branch |
| 58 | * ~~Conrad will look at Sphinx for adding link for "all methods even from base classes" |
| 59 | - ~~{{{: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. |
| 60 | * Greg will implement documentation virtual overlay symlink target |