Skip to content

3.12.0-release candidate 1 #2273

Closed
Closed

Description

@justinclift

Am now merging the outstanding commits from master branch to v3.12.x, for then building the release candidate 1 binaries from.

So far, these ones are merged and seem ok (some needed minor editing to merge cleanly):

I'm not sure what needs to be done for this one. Is there a commit in master I can merge, or set of them? 😄

It seems related to #2235, which is already merged.

Activity

  1. mgrojo commented on Jun 6, 2020

    @mgrojo
    Member

    @justinclift awesome!

    #2178 is fixed by #2235, so it should be fine now.

  2. justinclift commented on Jun 6, 2020

    @justinclift
    MemberAuthor

    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.

  3. justinclift commented on Jun 6, 2020

    @justinclift
    MemberAuthor

    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. 😄

  4. MKleusberg commented on Jun 6, 2020

    @MKleusberg
    Member

    Awesome 😄 Let me know when there are binaries for signing.

  5. justinclift commented on Jun 6, 2020

    @justinclift
    MemberAuthor

    @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).

  6. justinclift commented on Jun 7, 2020

    @justinclift
    MemberAuthor

    @MKleusberg The binaries are ready to sign. They're in the winXX-prerelease directories on the nightlies server. 😄

  7. justinclift commented on Jun 8, 2020

    @justinclift
    MemberAuthor

    k, the release candidate build has been published. 😄

  8. removed
    release blockerBugs that are serious enough to block our next release
    on Jun 8, 2020
  9. csanyipal commented on Jun 13, 2020

    @csanyipal

    @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

  10. justinclift commented on Jun 13, 2020

    @justinclift
    MemberAuthor

    @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.

  11. justinclift commented on Jun 25, 2020

    @justinclift
    MemberAuthor

    Oops. As a data point, I typo'd the git tag name for the 3.12.0 release. 3.12.0 vs v3.12.0.

    Just fixed it - needed to force push tags and recreate the release here on GitHub. Hopefully there's no residual weirdness. 😱

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions