We've published the beta3 binaries for our 3.11.0 release. I think we're mostly good now for getting 3.11.0 out the door:

• Get signing certificates for Windows (@MKleusberg)
  • Ideally we should have the signing be an automatic part of our nightly build process
  • Certificate has arrived (2019-01-23).
  • Now we just need to figure out how to sign stuff. The Certum smart card reader + bits seem super picky and flaky, and also seem to be windows only. 🙁
• Double check the status of all languages
  • All languages will need updating again, as new SQLCipher dialog text was added today.
  • The SQLCipher dialog is needed, as that lets us use SQLCipher 4.0.1 which avoids the new Magellan bug.
• Update the strings in the v3.11.x branch again, for the new SQLCipher dialog.
  • Done. 66172ac
• The new SQLCipher dialog needs translating for all languages.
  • sqlb_ar_SA.ts
  • sqlb_cs.ts
  • sqlb_de.ts
  • sqlb_es_ES.ts
  • sqlb_fr.ts
  • sqlb_it.ts
  • sqlb_ko_KR.ts
  • sqlb_pl.ts
  • sqlb_pt_BR.ts
  • sqlb_ru.ts
  • sqlb_tr.ts
  • sqlb_uk_UA.ts
  • sqlb_zh.ts
  • sqlb_zh_TW.ts
• Compile the math extension for macOS
  • Done. 7fbd89a
• For the Windows installer, should we update the final dialog (which .exe to launch SQLite vs SQLCipher) for the release?
  • Updated enough. We don't really require the dialog offering to launch DB4S, so we'll skip it instead. 😄
• Use SQLCipher 4.0.1.
  • The SQLCipher 4.x dialog change has been cherry-picked across to the v3.11.x branch
• Fix DBHub.io bug #116, so the DB4S <-> DBHub.io integration works.
  • Without this, people can't update their existing remote databases without renaming them on each save. 😦
  • The problem turned out to be the server giving a bad url in a request response, which subsequent requests tried to make use of and then hit problems. It's been fixed server side, but existing databases that have been uploaded via DB4S will probably still need renaming (once) when uploading, so an upload succeeds + they get new (correct) metadata to use for subsequent requests.
• DB4S bug run highlighted part of query only not working in beta3 #1708 sounds like it could be important to fix first
  • Fixed by @MKleusberg in 03d39bb