Attendees

• Eric, TomG, Greg

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

• Remove script tags from log on session restore
  • Greg added this security filtering so opening a session cannot execute arbitrary code included in the session.

• ChimeraX 1.2 release plan
  • Code freeze starting now except for bug fixes or safe changes, no new features
  • In one week create 1.2 branch but do not put build on download page. This is to allow new feature commits on develop for ChimeraX 1.3.
    • Remember to remove "devblahblahblah" from the core version number on the branch and "1.2dev..." from the dependency list in several bundles.
  • Daily build on download page will be built from develop branch.
  • If develop branch diverges from 1.2 branch then there will not be a 1.2 build on the download page, but the daily build will still provide testing of a very similar ChimeraX.
  • In two weeks replace ChimeraX 1.1 with 1.2 on download page but do not announce it.
  • In 4 weeks at end of April announce 1.2 release (or 1.2.1 if bug fixes were made after 1.2 was put on download page.

• Updates tool
  • Update interval menu entry is now on the tool panel.
  • Menu Tools / Utilities / Updates shows all available bundles. Change for 1.2 release so it initially shows only updates.

• Have "make install" force reinstall in bundles and core
  • Need to discuss this at next meeting.

• Test all existing Toolshed bundles with 1.2
  • Greg will do this.
  • Any tool that fails to install, or if the tool throws an error when menu entry used, will have ore requirement manually adjusted so it is not offered for install in ChimeraX 1.2.

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