Skip to content

5.11. Release Channels #76

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.

Sign up for GitHub

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 4 commits into from
Feb 13, 2016
Merged

5.11. Release Channels #76

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6645b64
translate release-channels
dalance Feb 9, 2016
564686a
update translation
dalance Feb 12, 2016
c78544b
update TranslationTable
dalance Feb 12, 2016
f9d080c
update translation
dalance Feb 13, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
104 changes: 59 additions & 45 deletions 1.6/ja/book/release-channels.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,52 +1,65 @@
% Release Channels
% リリースチャネル
<!-- % Release Channels -->

The Rust project uses a concept called ‘release channels’ to manage releases.
It’s important to understand this process to choose which version of Rust
your project should use.
<!-- The Rust project uses a concept called ‘release channels’ to manage releases. -->
<!-- It’s important to understand this process to choose which version of Rust -->
<!-- your project should use. -->
Rustプロジェクトではリリースを管理するために「リリースチャネル」という考え方を採用しています。どのバージョンのRustを使用するか決めるためには、この考え方を理解することが重要になります。

# Overview
<!-- # Overview -->
# 概要

There are three channels for Rust releases:
<!-- There are three channels for Rust releases: -->
Rustのリリースには以下の3つのチャネルがあります。

* Nightly
* Beta
* Stable

New nightly releases are created once a day. Every six weeks, the latest
nightly release is promoted to ‘Beta’. At that point, it will only receive
patches to fix serious errors. Six weeks later, the beta is promoted to
‘Stable’, and becomes the next release of `1.x`.

This process happens in parallel. So every six weeks, on the same day,
nightly goes to beta, beta goes to stable. When `1.x` is released, at
the same time, `1.(x + 1)-beta` is released, and the nightly becomes the
first version of `1.(x + 2)-nightly`.

# Choosing a version

Generally speaking, unless you have a specific reason, you should be using the
stable release channel. These releases are intended for a general audience.

However, depending on your interest in Rust, you may choose to use nightly
instead. The basic tradeoff is this: in the nightly channel, you can use
unstable, new Rust features. However, unstable features are subject to change,
and so any new nightly release may break your code. If you use the stable
release, you cannot use experimental features, but the next release of Rust
will not cause significant issues through breaking changes.

# Helping the ecosystem through CI

What about beta? We encourage all Rust users who use the stable release channel
to also test against the beta channel in their continuous integration systems.
This will help alert the team in case there’s an accidental regression.

Additionally, testing against nightly can catch regressions even sooner, and so
if you don’t mind a third build, we’d appreciate testing against all channels.

As an example, many Rust programmers use [Travis](https://travis-ci.org/) to
test their crates, which is free for open source projects. Travis [supports
Rust directly][travis], and you can use a `.travis.yml` file like this to
test on all channels:
<!-- New nightly releases are created once a day. Every six weeks, the latest -->
<!-- nightly release is promoted to ‘Beta’. At that point, it will only receive -->
<!-- patches to fix serious errors. Six weeks later, the beta is promoted to -->
<!-- ‘Stable’, and becomes the next release of `1.x`. -->
新しいnightlyリリースは毎日作られます。6週間ごとに、最新のnightlyリリースが「Beta」に格上げされます。これ以降は深刻なエラーを修正するパッチのみが受け付けられます。さらに6週間後、betaは「Stable」に格上げされ、次の「1.x」リリースになります。

<!-- This process happens in parallel. So every six weeks, on the same day, -->
<!-- nightly goes to beta, beta goes to stable. When `1.x` is released, at -->
<!-- the same time, `1.(x + 1)-beta` is released, and the nightly becomes the -->
<!-- first version of `1.(x + 2)-nightly`. -->
このプロセスは並行して行われます。つまり6週間毎の同じ日に、nightlyはbetaに、betaはstableになります。「1.x」がリリースされると同時に「1.(x + 1)-beta」がリリースされ、nightlyは「1.(x + 2)-nightly」の最初のバージョンになる、ということです。

<!-- # Choosing a version -->
# バージョンを選ぶ

<!-- Generally speaking, unless you have a specific reason, you should be using the -->
<!-- stable release channel. These releases are intended for a general audience. -->
一般的に言って、特別な理由がなければstableリリースチャネルを使うべきです。このリリースは一般のユーザ向けになっています。

<!-- However, depending on your interest in Rust, you may choose to use nightly -->
<!-- instead. The basic tradeoff is this: in the nightly channel, you can use -->
<!-- unstable, new Rust features. However, unstable features are subject to change, -->
<!-- and so any new nightly release may break your code. If you use the stable -->
<!-- release, you cannot use experimental features, but the next release of Rust -->
<!-- will not cause significant issues through breaking changes. -->
しかしRustに特に関心のある方は、代わりにnightlyを選んでも構いません。基本的な交換条件は次の通りです。nightlyチャネルを選ぶと不安定で新しいフィーチャを使うことができます。しかし、不安定なフィーチャは変更されやすく、新しいnightlyリリースでソースコードが動かなくなってしまうかもしれません。stableリリースを使えば、実験的なフィーチャを使うことはできませんが、Rustのバージョンが上がっても破壊的な変更によるトラブルは起きないでしょう。

<!-- # Helping the ecosystem through CI -->
# CIによるエコシステム支援

<!-- What about beta? We encourage all Rust users who use the stable release channel -->
<!-- to also test against the beta channel in their continuous integration systems. -->
<!-- This will help alert the team in case there’s an accidental regression. -->
betaとはどういうチャネルでしょうか？stableリリースチャネルを使う全てのユーザは、継続的インテグレーションシステムを使ってbetaリリースに対してもテストすることを推奨しています。こうすることで、突発的なリグレッションに備えることができます。

<!-- Additionally, testing against nightly can catch regressions even sooner, and so -->
<!-- if you don’t mind a third build, we’d appreciate testing against all channels. -->
さらに、nightlyに対してもテストすることでより早くリグレッションを捉えることができます。もし差し支えなければ、この3つ目のビルドを含めた全てのチャネルに対してテストしてもらえると嬉しいです。

<!-- As an example, many Rust programmers use [Travis](https://travis-ci.org/) to -->
<!-- test their crates, which is free for open source projects. Travis [supports -->
<!-- Rust directly][travis], and you can use a `.travis.yml` file like this to -->
<!-- test on all channels: -->
例えば、多くのRustプログラマが [Travis](https://travis-ci.org/) をクレートのテストに使っています。(このサービスはオープンソースプロジェクトについては無料で使えます) Travisは [Rustを直接サポート][travis] しており、「`.travis.yml`」に以下のように書くことですべてのチャネルに対するテストを行うことができます。

```yaml
language: rust
Expand All @@ -62,7 +75,8 @@ matrix:

[travis]: http://docs.travis-ci.com/user/languages/rust/

With this configuration, Travis will test all three channels, but if something
breaks on nightly, it won’t fail your build. A similar configuration is
recommended for any CI system, check the documentation of the one you’re
using for more details.
<!-- With this configuration, Travis will test all three channels, but if something -->
<!-- breaks on nightly, it won’t fail your build. A similar configuration is -->
<!-- recommended for any CI system, check the documentation of the one you’re -->
<!-- using for more details. -->
この設定で、Travisは3つ全てのチャネルに対してテストを行いますが、nightlyで何かおかしくなったとしてもビルドが失敗にはなりません。他のCIシステムでも同様の設定をお勧めします。詳細はお使いのシステムのドキュメントを参照してください。
8 changes: 8 additions & 0 deletions TranslationTable.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@
| compiler | コンパイラ
| constant | 定数
| constructor | コンストラクタ
| continuous integration | 継続的インテグレーション
| crate | クレート
| dangling | ダングリング
| declaration statement | 宣言文
Expand All @@ -46,6 +47,7 @@
| documentation comment | ドキュメンテーションコメント
| documentation test | ドキュメンテーションテスト
| early return | 早期リターン
| error | エラー
| enum | 列挙型
| equality | 等値性
| expression statement | 式文
Expand Down Expand Up @@ -83,18 +85,23 @@
| mutable binding | ミュータブルな束縛
| offline | オフライン
| opaque | オペーク
| open source | オープンソース
| option | オプション
| output lifetime | 出力ライフタイム
| owner | 所有者
| ownership | 所有権
| panic | パニック
| parametric polymorphism | パラメトリック多相
| patch | パッチ
| pattern | パターン
| performance | パフォーマンス
| platform | プラットフォーム
| pointer | ポインタ
| process | プロセス
| re-assignment | 再代入
| rebind | 再束縛
| regression | リグレッション
| release | リリース
| return | 返す
| scope | スコープ
| script | スクリプト
Expand Down Expand Up @@ -126,5 +133,6 @@
| variable binding | 変数束縛
| variant | ヴァリアント
| vector | ベクタ
| version | バージョン
| warning | ウォーニング
| wildcard | ワイルドカード