Next stable release on docker?

[EVaisman]

I see that the docker image with the latest tag has been updated recently. We currently point the redash docker image to the 10.1.0 tag (which is marked as the latest in the releases page). Updating it to point to lastest tag is a bit risky for us and we'd like the version to be explicitly specified. Is it possible to update the latest fixed version?

[justinclift]

The next production suitable release is likely to be available early in the new year. 😄

The preview tag isn't really suitable for production use yet, so you're probably best to stick with the older 10.1.0 release for now. 😅

[M-arghandiwal]

Is there an exact date?

[justinclift]

Nope, not yet.

[rodrigost23]

It's almost March already. Is there a roadmap, a list of issues that need to be fixed before release or something?

[eradman]

I proposed a change that I think can help us make progress:

Publish preview Docker image when release candidate is tagged: #6787

We can see that many people have been using the preview image, which is great, but bug reports are hard to follow because each person may be testing a different snapshot. With this change we should be connect bug reports and confirmation of fixes with specific tags:

24.01.0-dev
24.02.0-dev
24.03.0-dev
...

In integration tests this also makes the previous and next version predictable, so we can step through each release without having to pin an image to individual SHA1s

--- a/redash-email/docker-compose.yml
+++ b/redash-email/docker-compose.yml
@@ -2,7 +2,7 @@
 # For a production example please refer to getredash/setup repository on GitHub.
 version: "2.2"
 x-redash-service: &redash-service
-  image: redash/redash:preview
+  image: redash/preview:24.02.0-dev
   env_file:
     - .env

[rodrigost23]

It's already June, and we're stuck with EOL versions of Python, boto3, and so on, despite the fact that there isn't yet a stable version that's not at least three years old.

I'm not asking for new features, just for a version with up-to-date dependencies that is considered stable...

[zachliu]

@justinclift omg yes yes, i saw the same behavior similar behavior and thought something went wrong with my db migration too!!! i'm not using embeds but somehow ppl couldn't download their query results. when they go to the "download url" they got an empty page {"message": "No cached result found for this query."}

But in my case, i told everyone to re-run their queries manually so that the "cache" got the results 🤔

[justinclift]

Wish that worked for me when I tried it. 😉

[rcheatham-q]

I also would love to see a stable version released soon

[TheRaLabs]

i am begging you to have a stable release

[justinclift]

@TheRaLabs Give it a few weeks. I'm personally switching to focus full time on Redash development next week, so will be able to get the last remaining issues (like the above) fixed then.

[eradman]

I started a wiki page for Release Notes based on the -dev snapshots

@EVaisman @bear0330 @moontalk @nhayato @dtaniwaki @tsawada @rodrigost23 @kaelaela please take some time to update this page

[zachliu]

you guys are truly great! and i mean it!
when pestering opensource maintainers for new releases, the responses i usually got was you didn't pay for it, so shut up and wait 😂

[justinclift]

Heh Heh Heh. Yeah, some projects have a less-than-friendly Community. 😦

[phillipjohnson]

Bumping this to see if we have any update on a stable release? The release notes and tags for the DEV releases are helpful!

[justinclift]

The currently monthly release is pretty decent. I'm having to sort out some personal stuff currently though, so probably won't be looking at Redash with serious effort until the new year. 😦

[eradman]

I have deployed 24.11 widely and have had zero issues. The only thing I would so is apply to this branch is #7240 to a avoid a spurious warning.

I'd say we just need a ticket titled "v24.11 Release Plan"! @phillipjohnson does it make sense to you to target 24.11, 24.12 or wait for 25.01 to be tagged?

[phillipjohnson]

@eradman That's awesome! No preference on which version is best to tag as a release. If there is a list of items that need to be completed before an official release, I'd be happy to take a look and see where we can help out. Other than adjustments to the docker-compose file, if there are any manual steps required for an upgrade, that would be helpful. cc: @zachliu who had success with an upgrade based on comment below.

[eradman]

Next we should review the release checklist template to see if there are any steps we should add

https://github.com/getredash/redash/wiki/New-version-release-checklist

[eradman]

A regression was reported in #7247, I'm looking into this before starting a release ticket.

[mjgp2]

I'm going to be upgrading a v10 to v24 (when it's released).

Can I offer any help writing any migration docs, or are they somewhere already that I haven't found?

Thanks :)

[zachliu]

maybe a new migration section at https://redash.io/help (https://github.com/getredash/website)?

i want to brag about meself going from 9.0.0-beta to 24.10.0-dev 💪
i'd say i ironed out most if not all bumps already, with #6954 being the most significant one