-
Notifications
You must be signed in to change notification settings - Fork 631
Translate Ruby 3.4.3 Released (zh_tw) #3547
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
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
--- | ||
layout: news_post | ||
title: "Ruby 3.4.3 發布" | ||
author: k0kubun | ||
translator: "Bear Su" | ||
date: 2025-04-14 08:06:57 +0000 | ||
lang: zh_tw | ||
--- | ||
|
||
Ruby 3.4.3 已經發布了。 | ||
|
||
這是包括修復小型錯誤的例行更新。 | ||
詳細的變動請參閱 [GitHub 發布](https://github.com/ruby/ruby/releases/tag/v3_4_3)。 | ||
|
||
## 發布時程 | ||
|
||
我們打算每 2 個月發布一次最新的穩定 Ruby 版本(目前為 Ruby 3.4)。 | ||
我們預計 Ruby 3.4.4 於 6 月發布、Ruby 3.4.5 於 8 月發布、Ruby 3.4.6 於 10 月發布、Ruby 3.4.7 於 12 月發布。 | ||
|
||
如果有任何變更影響到相當多的人,我們可能會比預期更早發布新版本。 | ||
|
||
## 下載 | ||
|
||
{% assign release = site.data.releases | where: "version", "3.4.3" | first %} | ||
|
||
* <{{ release.url.gz }}> | ||
|
||
SIZE: {{ release.size.gz }} | ||
SHA1: {{ release.sha1.gz }} | ||
SHA256: {{ release.sha256.gz }} | ||
SHA512: {{ release.sha512.gz }} | ||
|
||
* <{{ release.url.xz }}> | ||
|
||
SIZE: {{ release.size.xz }} | ||
SHA1: {{ release.sha1.xz }} | ||
SHA256: {{ release.sha256.xz }} | ||
SHA512: {{ release.sha512.xz }} | ||
|
||
* <{{ release.url.zip }}> | ||
|
||
SIZE: {{ release.size.zip }} | ||
SHA1: {{ release.sha1.zip }} | ||
SHA256: {{ release.sha256.zip }} | ||
SHA512: {{ release.sha512.zip }} | ||
|
||
## 發布紀錄 | ||
|
||
許多提交者、開發者和漏洞回報者幫助了此版本的發布,在此感謝所有人的貢獻。 |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about
「如果有任何改動會影響到相當多的人,這些版本可能會提前釋出。」 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good for me.
The wording is also used in previous posts:
If we change to 「如果有任何改動會影響到相當多的人,這些版本可能會提前釋出。」, I want to update these files in another PR. Is it a good idea?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh nice, my bad—I didn’t realise it was the same wording as before. Let’s keep it then. Thanks!