You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is that the only stuff we need to merge before generating the new builds for Win and macOS?
I'm thinking we do that, and get people testing those. Meanwhile we generate updated strings for translation and apply the new translation updates that come in.
That should mean we have a fairly well tested code base (v3.12.x branch) to generate the final release binaries from in a week or so.
Hmmm, it's just about to hit 1am here. I'll get some sleep now, and build the binaries in the morning.
If there are more changes that need cherry-picking to our v3.12.x branch, feel free to do them directly or leave a note here, and I'll get to them after I wake up. Will build the rc1 binaries from there. 😄
@MKleusberg Any idea about #2200? It's marked as a release blocker, but maybe it's not?
I just update my Sqlitebrowser here on Ubuntu. Now I am running this version of sqlitebrowser:
Version 3.12.99 (Jun 11 2020)
Built for x86_64-little_endian-lp64, running on x86_64
Qt Version 5.9.5
SQLCipher Version 4.3.0 community (based on SQLite 3.30.1)
The issue #2200 still exists. So in fact I can not use sqlitebrowser here, on Ubuntu 18.04.4 LTS
@csanyipal Ouch, that's not good. Looks like it still needs fixing after all. 😦
Ahh, just noticed your screencast in the original issue report. That should help. 😄
With the version numbering, 3.12.99 (Jun 11 2020) means you're running our latest development code (master branch in git) rather than 3.12.0-release candidate 1.
Activity
mgrojo commentedon Jun 6, 2020
@justinclift awesome!
#2178 is fixed by #2235, so it should be fine now.
justinclift commentedon Jun 6, 2020
Thanks, wasn't sure. 😄
Is that the only stuff we need to merge before generating the new builds for Win and macOS?
I'm thinking we do that, and get people testing those. Meanwhile we generate updated strings for translation and apply the new translation updates that come in.
That should mean we have a fairly well tested code base (v3.12.x branch) to generate the final release binaries from in a week or so.
justinclift commentedon Jun 6, 2020
Hmmm, it's just about to hit 1am here. I'll get some sleep now, and build the binaries in the morning.
If there are more changes that need cherry-picking to our
v3.12.xbranch, feel free to do them directly or leave a note here, and I'll get to them after I wake up. Will build the rc1 binaries from there. 😄MKleusberg commentedon Jun 6, 2020
Awesome 😄 Let me know when there are binaries for signing.
justinclift commentedon Jun 6, 2020
@MKleusberg Any idea about #2200? It's marked as a release blocker, but maybe it's not?
Similar thought for #2113, there seems to be an outstanding piece for that, but I'm not sure if that is something for another day (etc).
justinclift commentedon Jun 7, 2020
@MKleusberg The binaries are ready to sign. They're in the winXX-prerelease directories on the nightlies server. 😄
justinclift commentedon Jun 8, 2020
k, the release candidate build has been published. 😄
csanyipal commentedon Jun 13, 2020
The issue #2200 still exists. So in fact I can not use sqlitebrowser here, on Ubuntu 18.04.4 LTS
justinclift commentedon Jun 13, 2020
@csanyipal Ouch, that's not good. Looks like it still needs fixing after all. 😦
Ahh, just noticed your screencast in the original issue report. That should help. 😄
With the version numbering,
3.12.99 (Jun 11 2020)means you're running our latest development code (masterbranch in git) rather than 3.12.0-release candidate 1.justinclift commentedon Jun 25, 2020
Oops. As a data point, I typo'd the git tag name for the 3.12.0 release.
3.12.0vsv3.12.0.Just fixed it - needed to force push tags and recreate the release here on GitHub. Hopefully there's no residual weirdness. 😱