v25.1 Release Plan

[eradman]

• Create a release branch
• Create new GitHub Release
• Push image to Docker Hub
• Update Redash website
• Announcement in discussions/6647

References:

New-version-release-checklist
v6 Release Plan
Release Notes
Release Candidates and Release Versioning

[justinclift]

We'll probably need to make sure the tag that's created doesn't have leading zero's in the month part too. ie 25.1 vs 25.01

[lucydodo]

Should we write release notes?

[justinclift]

@eradman has already been creating release notes in the wiki: https://github.com/getredash/redash/wiki/Release-Notes 😄

[eradman]

We'll probably need to make sure the tag that's created doesn't have leading zero's in the month part too. ie 25.1 vs 25.01

Do we want to drop the leading zero? As long as we're consistent in the future either way is fine.

This is is the sequence I have in mind:

git checkout 25.01.0-dev
git checkout -b v25.1
vim package.json redash/__init__.py pyproject.toml  # set version to 25.1.0
git commit -a -m "25.1.0 release"
git push --set-upstream origin v25.1
gh release create v25.1.0 --target v25.1 --title v25.1.0 --notes "v25.1.0 release"

In this scheme any bug fixes and patches can be applied to the v25.1 branch, followed by a minor release.

[justinclift]

Do we want to drop the leading zero?

Yeah, we definitely do. It has the potential (and likelihood) of causing issues with things that can't deal with leading zeros, and we don't really need to take that chance.

@arikfr Pointed out a while ago that it'll probably cause issues with older versions of Redash that are doing version checks too, so we should fix the problem before the next release.

This is is the sequence I have in mind ...

Looks good to me, nothing is immediately jumping out as wrong with that. 😄