3.11.1 - outstanding pieces

[justinclift]

• Edit box is not updated at all (as in 'Browse Data') when in 'Execute SQL' #481 - Edit box is not updated at all (as in 'Browse Data') when in 'Execute SQL'
• DB Browser Crashes When Importing Its Own .sql dump #1045 - DB Browser Crashes When Importing Its Own .sql dump
• Updated query optimisations #1161 - Updated query optimisations
• Network inaccessible error when using a WiFi network #1595 - Network inaccessible error when using a WiFi network
• "determining row count" displays forever in Browse Data tab #1654 - "determining row count" displays forever in Browse Data tab
• About Info - display 32bit vs 64bit #1660 - About Info - display 32bit vs 64bit
• [Feature Request-Execute SQL] Allow bottom editor of Execute SQL tab to grow taller. #1670 - Allow bottom editor of Execute SQL tab to grow taller
• TEXT values show as BLOB #1731 - TEXT values show as BLOB
• Error encrypting in 3.11.0 #1732 - Error encrypting in 3.11.0
• It's not possible to modify some tables #1733 - It's not possible to modify some tables
• Class 'NullLineEdit' lacks Q_OBJECT macro #1740 - Class 'NullLineEdit' lacks Q_OBJECT macro
• - Include SQLite 3.27.1 instead of SQLite 3.26.0
• Night Mode or Dark Theme #1493 - Night Mode or Dark Theme
  • Unlikely to be solved any time soon, as dark mode support seems to still be "in progress" for Qt itself. We can't complete this for all supported OS's until Qt itself reasonably supports them. eg:
    • Windows (Qt bug here)
    • macOS (QtLabel wrong colour)
  • We'll just note Dark Mode theme support is known to be broken on Windows and macOS.

Building new release binaries right now. 😄

[mgrojo]

Should we just release 3.11.1 "as is" and update the Release Notes to say we don't yet support Dark Mode at all?

In Linux, it works like a charm 😉 but yes I agree on releasing as is and publicize that it is not yet supported in Windows and Mac.

I think there are other bug fixes that we could consider for including in v3.11.1 if they are simple enough, for example, after making a quick review:
7e549c7
1925ccf
0ffed5e
79ffd77
58f52f1

[justinclift]

I think there are other bug fixes that we could consider ...

Yeah, they all look pretty simple, and unlikely to break anything. It's fine to commit those (and any other simple looking stuff you want) to the 3.11.x branch. 😄

[justinclift]

In Linux, it works like a charm 😉 but yes I agree on releasing as is and publicize that it is not yet supported in Windows and Mac.

Been thinking over this today. Yeah, I think that'll be the way to go. 😄

[mgrojo]

Yeah, they all look pretty simple, and unlikely to break anything. It's fine to commit those (and any other simple looking stuff you want) to the 3.11.x branch. 😄

Am I still on time for adding those commits?

[justinclift]

Yeah, go for it. Still doing builds to test #1595 at the moment. Might not have everything wrapped up for another day anyway. 🤷‍♂️

[mgrojo]

I've cherry-picked only three of the commits. The remaining ones, although simple, raise conflicts, so it would require time to fix and check. For the moment, I leave it as is.

[justinclift]

Thanks heaps @mgrojo, sounds good. 😄

[justinclift]

@MKleusberg Windows 3.11.1 binaries are ready for signing:

• https://nightlies.sqlitebrowser.org/win32-prerelease/DB.Browser.for.SQLite-3.11.1-win32.msi
  • SHA256: 9adfece6d45397031877cc02252a3caf2b09c1524787d262b0e7371e259ad82d
• https://nightlies.sqlitebrowser.org/win32-prerelease/DB.Browser.for.SQLite-3.11.1-win32.zip
  • SHA256: 41d2a1ec3d7327827ff827ece0a9ca4ee11225b8c0bb81a44b0b456d3c33350f
• https://nightlies.sqlitebrowser.org/win64-prerelease/DB.Browser.for.SQLite-3.11.1-win64.msi
  • SHA256: a7be5182c7a504926cfeded339e580917950af0465efc730001dc0fa9fce5d30
• https://nightlies.sqlitebrowser.org/win64-prerelease/DB.Browser.for.SQLite-3.11.1-win64.zip
  • SHA256: 92ddd5069222bb531bb378e8fe608701978627aa0ae9e9d7aa3127b2d6cc5caf

When that's done, there's a new (Draft status) 3.11.1 Release ready to receive them. The SHA256 checksums at the bottom will need updating for the new signed version of the files.

The macOS binary has already been signed and attached to the new release, so you're ok to hit the Publish button when the Windows ones are added. 😄

[MKleusberg]

Aaand it's published 😄 I have already updated the README file and the issue templates in the master branch. The binaries still need to be uploaded to our Website plus updating of the website itself. When that's done, the currentrelease file can be updated.

[justinclift]

Excellent, thanks heaps!

I'm about to get some sleep, so will get all this stuff done after that. 😄

[justinclift]

The download cluster and main website have been updated for 3.11.1. 😉

[justinclift]

Its been 24 hours, and no major show-stopper type bugs have been reported yet.

I've just updated the currentrelease file, so the update prompt starts happening for people. 😄