| | 30 | * Will we drop macOS 10.14 in ChimeraX 1.5? |
| | 31 | * Plan is to keep macOS 10.14 for ChimeraX 1.5 |
| | 32 | * About 100 unique IP addresses per month download from macOS 10.14. |
| | 33 | * Currently Mac universal 10.15, Mac ARM 11, and Mac Intel 10.14 daily builds are made and on the download page in that order. |
| | 34 | * We could use the same for the 1.5 release, including 10.14 on Intel. |
| | 35 | * We could optionally improve the download page to show only the Mac universal build or if the browser user-agent says Mac 10.14 show only the Intel Mac build. The other builds would be under "other releases". |
| | 36 | * Download page improvement can be done any time before or after release. |
| | 37 | |
| | 38 | * Toolshed bundle requirement checking |
| | 39 | * Eric says this is about having the Toolshed verify more than the core version number before installing a bundle. |
| | 40 | * This will be long discussion for another meeting. |
| | 41 | |
| | 42 | * Update UniRef BLAST databases |
| | 43 | * Elaine would like the databases updated for ChimeraX 1.5 |
| | 44 | * These are entirely handled by the back-end blast web service so in theory can be updated any time, not coordinated with release. |
| | 45 | * Ticket is assigned to Scooter. |
| | 46 | * Greg found 2021 versions of databases on Wynton that could be used. But require making the blast database files. |
| | 47 | * Scooter indicated by email that milestone for 1.6 is more practical given his limited time. |
| | 48 | |
| | 49 | * Mingw compiler on Windows |
| | 50 | * Zach has tried using the mingw compiler on Windows instead of our current Microsoft Visual Studio. |
| | 51 | * This compiler was easier to use with github actions. |
| | 52 | * Also apparently did not use cygwin. |
| | 53 | * Seems like a major change. |
| | 54 | |
| | 55 | * Have github convert line endings? |
| | 56 | * Zach suggests having git auto-convert text file line endings to use LF and no CR LF in repository. |
| | 57 | * TomG suggests this seems not worth the possible debugging that will result. |
| | 58 | * Zach says it is to help outside developers contributing on Windows to our repository. We don't have any currently. |