v0.25.0 Release watch

[kamikazechaser]

This is a tracker of when v0.25.0 is expected to be released.

Docs and dependencies:

• Changelog updated
• Core dependencies updated
• /x dependencies updated
• /tools dependencies updated
• base.go Version

Pending PRs:

• feat(*): correct panic error #758
• Archived tasks that are trimmed from the set are deleted #743
• Implement reusing redis client #742
• feature: configurable janitor interval and deletion batch size #715
• feat(*): update CHANGELOG.md file #708
• [FEATURE REQUEST] maxArchiveSize and archivedExpirationInDays should be configurable at the server level #534

Pending Issues:

• [BUG] cant install asynq/tools/asynq@v0.21.0 #578

To test the latest changes, you can always install from the @master branch.

[shuqingzai]

Does #787 have any plans? @kamikazechaser

[kamikazechaser]

@shuqingzai I'd put it for the next release. Anyways after v0.25.0 I expect development and feature releases to be much much faster as we would have sorted some of the main blockers.

[xinjiayu]

I hope to add a feature that automatically sets the client name when asynq connects to redis, which makes it convenient to check the connection status of asynq on redis. Thank you.

[pior]

@kamikazechaser do you think #868 can end up in this release?

This change is a significant performance improvement, and is pretty common practice.

[kamikazechaser]

@pior There are a few related issues/PRs to that. But most likely not. I'll post an update on this release by next week.

[pior]

All right 👍
What should we expect for this PR (and the other you mention)? Will there be another release soon?

We would really prefer an active Asynq repo, to maintaining a fork 🙏

[kamikazechaser]

Just quick update, v0.25.0 will be prepped for release next week. You can expect it to be out within the next 2 weeks. Additionally, new major feature changes PRs will be first merged into the unstable branch so that users can test it out with go get github.com/../..@unstable without having to wait for a tagged release. unstable will be free of breaking changes.

[pior]

Sweet!
What kind of changes would go to unstable? Would #868 be a good candidate?

[kamikazechaser]

Yeah, pretty much all new useful features that also need time for continuous feedback (smoke testing sort of branch).

[kamikazechaser]

I don't have permissions to push to forks. So, there is a bit of hold up on small issues that need resolving on those PRs. But by the end of the week I'll change the base, merge them on a different one so that we can proceed with closing this issue asap.