Attendees

• Eric, TomG, Greg, Tristan

Agenda

• Action items
• ChimeraX
  • Ready to release?
    • Release plan is to have all ChimeraX 1.2 code changes in by April 1 meeting
    • Version 1.2 will be called a release candidate initially and promoted to official release if stable for some weeks
    • If fixes to 1.2 release candidate needed, will put out 1.2.1
  • Toolshed tickets
  • Should we remove the HTML tool tutorial and promote only Qt GUIs?
  • GitHub found 7 vulnerabilities on RBVI/ChimeraX's default branch (6 high, 1 moderate). To find out more, visit: remote: ​https://github.com/RBVI/ChimeraX/security/dependabot
  • Have "make install" actually install things
• Chimera

Discussion

• 1.2 release
  • 1.2 branch was made two days ago
  • Eric and Tom still fixing bugs
  • Will check with each other by email next Tuesday and put 1.2 release candidate on download page if ready.
  • Greg says putting release candidate on download page will involve a little hand work to change file system links.

• Version numbers for bundles
  • Greg suggests all bundles in distribution that have changed since 1.1 should have updated version numbers, so new distribution reflects that the bundle changed.

• Make install not installing
  • In core a "make install' won't install if the version number of core has not increased. Have to use make "reinstall".
  • Easy to forget this when debugging and waste time before realizing none of the debugging code changes were installed.
  • "make install" for bundles works because bundle_builder is used. But core does not use it.
  • Would prefer that "make install" does the install even with same version number.
  • Another scenario from Eric: make install in bundles after atomic_lib change of C++ Ring class to rebuild 10 bundles that depend on atomic_lib didn't install any.
  • Greg mentions that pip --force option used to force reinstall does not update dependencies.
  • Discussed whether pip uninstall followed by pip install could solve some of these install problems when version number does not change.
  • Should make some tickets for the build system problems.

Action Items

• Tell Tristan about 1.2 release dates - TomG
• Make Updates tool started from menu Tools / Utilities / Updates show only updates, not all available bundles - Greg
• Change milestone on all 1.2 enhancement tickets that won't be in 1.2 to milestone 1.3 - Greg
• Add check frequency menu to Toolshed updates tool - Greg
• Check that all Toolshed bundles that install in 1.2 actually start -- add core<1.2 dependency to those that fail - Greg