Skip to content

Add blog announcing-etcd-3.6.md #999

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

Merged
merged 1 commit into from
May 15, 2025
Merged

Add blog announcing-etcd-3.6.md #999

merged 1 commit into from
May 15, 2025

Conversation

ahrtr
Copy link
Member

@ahrtr ahrtr commented May 12, 2025

We are releasing etcd v3.6.0 on May 15th, 2025 (Thursday), so we are targeting to publish the blog on the same day, right after the release of v3.6.0.

cc @fuweid @ivanvc @jberkus @jmhbnz @serathius @spzala PTAL, thx

Copy link
Member

@spzala spzala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work, thanks @ahrtr - putting all these together is a lot of work! Lgtm except few small inline comments.

@ahrtr ahrtr force-pushed the blog_3.6.0 branch 2 times, most recently from 789f632 to 4e86dc7 Compare May 12, 2025 16:30
@spzala
Copy link
Member

spzala commented May 12, 2025

@ahrtr thanks so much for quickly addressing my comments!

@ahrtr ahrtr force-pushed the blog_3.6.0 branch 5 times, most recently from fa3bd24 to 8a074c2 Compare May 12, 2025 18:23
@ahrtr
Copy link
Member Author

ahrtr commented May 12, 2025

Thanks @spzala for the quick review!!!

All comments resolved and all workflows are green. Please other reviewers take a look. thx

Copy link
Member

@jmhbnz jmhbnz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow great summary @ahrtr nice work!

A couple minor suggestions below but I think this looks great.

Let's hold for other reviewers
/hold

@ahrtr ahrtr requested review from jberkus, serathius, fuweid and ivanvc May 12, 2025 20:48
@ahrtr ahrtr force-pushed the blog_3.6.0 branch 2 times, most recently from 189cfa5 to 9098ca4 Compare May 13, 2025 11:52
Copy link
Contributor

@jberkus jberkus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly minor edits, but I think we should move up a bunch of stuff, like Performance, to Features, instead of having it below Breaking Changes.

@jberkus
Copy link
Contributor

jberkus commented May 13, 2025

Link check completed.

Ready to go.

@ahrtr
Copy link
Member Author

ahrtr commented May 13, 2025

Thanks all for the review!!! I really appreciate it. I will merge this PR right after I release etcd v3.6.0 on May 15th (Thursday). Leave this PR to me. Thanks again!!!

Copy link
Contributor

@nate-double-u nate-double-u left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A copy-edit pass. Feel free to take or leave any suggestion in particular.

Through the etcd-operator Working Group, we plan to improve usability as well.

What follows are the most significant changes introduced in etcd v3.6.0, along with the discussion of the
roadmap for future development. For a detailed list of changes, please refer to the [CHANGELOG-3.6][].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
roadmap for future development. For a detailed list of changes, please refer to the [CHANGELOG-3.6][].
roadmap for future development. For a detailed list of changes, please refer to [CHANGELOG-3.6][].

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like it's better to keep the the, it highlights a specific changelog (changelog-3.6)

_**Figure 1:** Memory usage comparison between etcd v3.5.20 and v3.6.0-rc.2 under different read/write ratios.
Each subplot shows the memory usage over time with a specific read/write ratio. The red line represents etcd
v3.5.20, while the teal line represents v3.6.0-rc.2. Across all tested ratios, v3.6.0-rc.2 exhibits more
stable and lower memory usage._
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
stable and lower memory usage._
stability and lower memory usage._

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The intention is to use an adjective stable, but the original expression might be a little confusing, so just changed

from

more stable and lower memory usage

to

lower and more stable memory usage

@ahrtr ahrtr force-pushed the blog_3.6.0 branch 2 times, most recently from cf727c9 to 9a3a248 Compare May 14, 2025 17:55
@ahrtr ahrtr force-pushed the blog_3.6.0 branch 2 times, most recently from 38f80e0 to c2e0fd9 Compare May 15, 2025 12:28
Signed-off-by: Benjamin Wang <[email protected]>
Copy link
Member

@ivanvc ivanvc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was finally able to read this (sorry for being late to the party). This is great. Great job leading, Benjamin, and everyone who contributed to this blog post ❤️

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, fuweid, ivanvc, jberkus, jmhbnz, serathius, spzala

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [ahrtr,ivanvc,jberkus,jmhbnz,serathius,spzala]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jberkus jberkus merged commit 20f8339 into etcd-io:main May 15, 2025
6 checks passed
@ahrtr
Copy link
Member Author

ahrtr commented May 15, 2025

@jberkus thanks. Timing is good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants