-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plans for upcoming twemproxy release lines #608
Comments
This was referenced Jun 30, 2021
Closed
@TysonAndre I'm curious if there are any plans of releasing new version? |
马晓栋已经收到您的来件,谢谢!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(Having been added as a collaborator yesterday)
Release lines
0.4.x
The 0.4.x release line will contain bug fixes and new unit/integration tests (for bugs that already have proposed fixes that are expected to be correct).I plan to discontinue this release line when 0.5.0 is published.0.5.x
The 0.5.x releases will contain new features that are likely to not impact existing use cases, e.g. support for new redis and memcache commands, some config file and CLI options, etc.
I plan to discontinue this release line when 0.6.x has been released for a while and validated
See https://github.com/twitter/twemproxy/blob/master/ChangeLog
A release candidate can be found at https://github.com/twitter/twemproxy/releases/tag/v0.5.0-RC
0.6.x
I plan to include several new major features in the 0.6.x release line that refactor the way connections are made:
The heartbeat/failover pool patches for memcached/redis (failover is strongly recommended only for memcached, redis would have redis sentinel).
(with additional patches)
This was originally proposed at rebase heartbeat branch #428
The redis sentinel patches, originally proposed at twemproxy work with redis-sentinel #324
(with additional bug fixes and support for new redis server/sentinel versions)
These features can be previewed at the forked repository https://github.com/ifwe/twemproxy/releases/tag/0.5.2-tmg19 (changes on that fork correspond to what is planned for twitter/twemproxy's 0.6.0) but additional changes and fixes may be made by the time 0.6.0 is officially released.
The text was updated successfully, but these errors were encountered: