Is the RC1 still fine to use? It's been a few months so I don't know if it's stable enough.

Ahhh. Grab the build from here for now then. It's just missing a translation update for one language from what will be the final thing (in theory):

https://github.com/sqlitebrowser/sqlitebrowser/releases/tag/v3.13.x-rc1

Note that if you're on windows though, it'll probably give you some warning about the package not being signed by a known developer. That's what we're still waiting on the external crowd for. 😉

Thank you

I apologize for the delayed release.
Recently we've been working on some changes to build process that we need to make, and I'm hoping to have that done by the end of the month at the latest, at which point we'll be able to consider a RC2 release, and maybe talk about a stable release again.

No apologies necessary, and I want to say this is terrific news. Thanks!

Heh Heh Heh. Any interest in making a PR with those additions?

Website repo is here: https://github.com/sqlitebrowser/website

😁

Yes - I left a couple questions at sqlitebrowser/website#22

Yes, I apologize for the delay, and we'll release next version as soon as possible. :)

I really want to thank you personally, your contributions and interest have kept me motivated, especially the recent work on 'CHANELOG', which has helpme our to write better release notes. Thank you. Have a great day.

Ideally we'll add a blog entry about the new release to the sqlitebrowser.org website.

Generally the release announcement info on our website is a fully worked blog post that's effectively a copy of the release announcement here on GitHub. i.e. same info, two different locations

@richb-hanover Any interest in making such a blog post on the website? 😄

@justinclift I think you're close to done. Here's what I would propose:

1. The "tag note" (at https://github.com/sqlitebrowser/sqlitebrowser/releases/tag/v3.13.0) already is the blog post. Move it there.
2. Shorten that tag note to the essentials and point readers to the full blog post
3. Add **New Version 3.13.0 - read the blog post** just below the headline on the home page so that occasional visitors to the site will learn about the new version. (This could go away in 30 to 60 days)
4. Rename the "About" tab (in the header) to "History" and move it between "Stats" and "Patreon" tabs
5. When you're feeling bold, post an announcement to Hacker News :-)

Rename the "About" tab (in the header) to "History" and move it between "Stats" and "Patreon" tabs

???

That seems weird. The "About" page for a project traditionally tells people about the project. Seems like a better name than History. 😄

@richb-hanover Any interest in making such a blog post on the website? 😄

I don't mind doing that if you want .. and slapping something on Twitter.

@chrisjlocke Looks like it's all yours. 😄

And I'm happy to let @chrisjlocke make suitable changes, and post to eX-Twitter.

The file will be updated someitme next week. (Delayed Rollout)
We intentionally update late to avoid any potential critical issues in the new relesae.

Yeah. We tend to wait a few days from the initial release just in case there's some critical issue that we hadn't spotted. It's happened before. 😉

When that file is updated (both here in the repo and on our download server), it triggers the majority of our existing users to upgrade too.

Sorry for late, currentrelease file has just been updated.

Heh Heh Heh. That's only one of the two places it needs to be done. 😉

The currentrelease file in the DB4S repo is only checked by really old versions of DB4S. Modern DB4S instead checks https://download.sqlitebrowser.org/currentrelease, which still needs updating:

$ curl https://download.sqlitebrowser.org/currentrelease
3.12.2
https://sqlitebrowser.org/blog/version-3-12-2-released

To change that, update the string here then run the deploy.sh script in the root user home directory on the download server:

https://github.com/sqlitebrowser/db4s_cluster_downloader/blob/5626f6687b8ac8d0d3a6c555e1c34ce4af5fd398/main.go#L199

Since it's a simple change, I just did it and updated the running server too. It's now live. 😄

How are you changing the number of fields in the table?

@RRROMAN123 If this is still a concern, please open a new issue. Thanks