Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Schrödinger's branch, or Ruby is dead every year
Search
Sponsored
·
Ship Features Fearlessly
Turn features on and off without deploys. Used by thousands of Ruby developers.
→
usa
May 31, 2018
Programming
790
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Schrödinger's branch, or Ruby is dead every year
RubyKaigi2018 LT
usa
May 31, 2018
More Decks by usa
See All by usa
Rubyの安定版を保守する意義 / Why we maintain stable versions of Ruby?
unak
0
190
WindowsにおけるRubyのエンコーディングの話 Ruby3版/Ruby's encoding on Windows at Ruby3
unak
0
470
PIXIV TECH FES. short session / What kind of contribution to OSS is really pleased?
unak
0
2.2k
Internal of the image processing required on the developing of web applications
unak
6
5.4k
talk about IO
unak
5
2k
Other Decks in Programming
See All in Programming
モジュールの視点からSwiftを読み解く #iosdc
s_shimotori
0
350
[2026-09-26]空論ジェネリックプロセス~テスト資産とAIで紡ぐ、再現可能なパフォーマンスチューニングの話~
tosite
0
260
20260914 AIエージェント時代のPlatform Engineering LLM基盤とプロダクトの責務境界線
kanfab1
7
2.4k
UPDATE をやめる — EF Core でマスタをバージョン管理する
panda728
PRO
0
1.1k
動作中のプログラムの中身をリアルタイムに覗く / Realtime Debugger for CSharp with Roslyn
prota
1
1.8k
Vue Fes Japan 2026 タイムテーブル徹底解説
448jp
1
630
Starting & Sustaining Code-Based E2E Testing for Non-Coding QA Teams( #jasstniigata )
teyamagu
PRO
1
910
iOSDC2026登壇資料.pdf
riofujimon
0
210
ソニーのクラウド共通基盤の変遷とAI時代の開発スタイルに合わせた進化 / The Journey of Sony’s Common Cloud Platform and Its Evolution for AI-Native Development
kenjiyoneyama
0
230
GitHubハンズオン講座 — 実務レベルのチーム開発のフローを身につけよう
junhat6
0
120
カツオ、ご期待ください
suneo3476
0
150
The Rails Doctrine Decade
koic
2
500
Featured
See All Featured
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
10k
Navigating Team Friction
lara
192
16k
jQuery: Nuts, Bolts and Bling
dougneiner
66
8.6k
Ethics towards AI in product and experience design
skipperchong
2
410
Bioeconomy Workshop: Dr. Julius Ecuru, Opportunities for a Bioeconomy in West Africa
akademiya2063
PRO
1
390
Side Projects
sachag
456
43k
The Hidden Cost of Media on the Web [PixelPalooza 2025]
tammyeverts
2
510
BBQ
matthewcrist
89
10k
The Art of Programming - Codeland 2020
erikaheidi
57
14k
Designing Powerful Visuals for Engaging Learning
tmiket
1
590
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
123
22k
How to Build an AI Search Optimization Roadmap - Criteria and Steps to Take #SEOIRL
aleyda
1
2.2k
Transcript
自己紹介 usa from Inc. (Sendagaya, Tokyo) @unak (Twitter
/ GitHub) Ruby Committer Windows port maintainer Stable versions branch maintainer
宣伝① は (だいたい) Rubyの会社です!
GitHubアカウントや 技術書等のURLで すぐにご応募可能! https://recruit.jobcan.jp/pixiv/entry/new/4057 宣伝①
開発サイクルを促進する クラウド画像変換サービス 宣伝②
まずはお問い合わせ! ImageFlux 宣伝②
SCHRÖDINGER'S BRANCH
SCHRÖDINGER'S BRANCH RUBY IS DEAD EVERY YEAR
Development Branch “trunk” BRANCHES
Development Branch “trunk” BRANCHES Commit! Commit! Commit! Commit! Commit! Revert!
Commit! Commit! Revert! Commit! Commit!
Development Branch “trunk” BRANCHES Merry Christmas! Stable Branch (e.g. “ruby_2_1”)
Development Branch “trunk” BRANCHES Stable Branch (e.g. “ruby_2_1”) 2.1.0 2.1.1
2.1.2
Development Branch “trunk” BRANCHES Merry Christmas! Stable Branch “ruby_2_1” Stable
Branch “ruby_2_2”
Development Branch “trunk” BRANCHES Stable Branch “ruby_2_1” Stable Branch “ruby_2_2”
2.2.0 2.1.5 2.1.6 2.2.1 2.2.2 2.1.7
Development Branch “trunk” BRANCHES Merry Christmas! Stable Branch “ruby_2_1” Stable
Branch “ruby_2_2” Stable Branch “ruby_2_3”
Development Branch “trunk” BRANCHES Stable Branch “ruby_2_1” Stable Branch “ruby_2_2”
Stable Branch “ruby_2_3”
Development Branch “trunk” BRANCHES Security only Branch “ruby_2_1” Stable Branch
“ruby_2_2” Stable Branch “ruby_2_3”
Development Branch “trunk” BRANCHES Security only Branch “ruby_2_1” Stable Branch
“ruby_2_2” Stable Branch “ruby_2_3” Merry Christmas! Stable Branch “ruby_2_4”
Development Branch “trunk” BRANCHES Security only Branch “ruby_2_1” Security only
Branch “ruby_2_2” Stable Branch “ruby_2_3” Stable Branch “ruby_2_4”
Development Branch “trunk” BRANCHES Security only Branch “ruby_2_1” Security only
Branch “ruby_2_2” Stable Branch “ruby_2_3” Stable Branch “ruby_2_4” EoL!!!
Development Branch “trunk” BRANCHES Security only Branch “ruby_2_1” Security only
Branch “ruby_2_2” Stable Branch “ruby_2_3” Stable Branch “ruby_2_4” Stable Branch “ruby_2_5” Merry Christmas!
Development Branch “trunk” BRANCHES Security only Branch “ruby_2_1” Security only
Branch “ruby_2_2” Security only Branch “ruby_2_3” Stable Branch “ruby_2_4” Stable Branch “ruby_2_5”
Development Branch “trunk” BRANCHES Security only Branch “ruby_2_1” Security only
Branch “ruby_2_2” Security only Branch “ruby_2_3” Stable Branch “ruby_2_4” Stable Branch “ruby_2_5”
Development Branch “trunk” BRANCHES Security only Branch “ruby_2_1” Security only
Branch “ruby_2_2” Security only Branch “ruby_2_3” Stable Branch “ruby_2_4” Stable Branch “ruby_2_5”
WHAT IS “EOL”? Never maintained (≒ Never committed) Never released
from the branch
WHAT IS “EOL”? Never maintained (≒ Never committed) Never released
from the branch Then, maybe “ruby_2_2” has died, but cannot predicate it…
If there are releases from another branches but not from
the branch, it means death WHAT IS “EOL”?
If there are releases from another branches but not from
the branch, it means death WHAT IS “EOL”? In other word, we can know its death only when “opening the box”
SCHRÖDINGER'S BRANCH