Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Schrödinger's branch, or Ruby is dead every year
Search
usa
May 31, 2018
Programming
0
720
Schrödinger's branch, or Ruby is dead every year
RubyKaigi2018 LT
usa
May 31, 2018
Tweet
Share
More Decks by usa
See All by usa
Rubyの安定版を保守する意義 / Why we maintain stable versions of Ruby?
unak
0
130
WindowsにおけるRubyのエンコーディングの話 Ruby3版/Ruby's encoding on Windows at Ruby3
unak
0
420
PIXIV TECH FES. short session / What kind of contribution to OSS is really pleased?
unak
0
2.1k
Internal of the image processing required on the developing of web applications
unak
6
5.1k
talk about IO
unak
5
1.9k
Other Decks in Programming
See All in Programming
ニーリーにおけるプロダクトエンジニア
nealle
0
790
「テストは愚直&&網羅的に書くほどよい」という誤解 / Test Smarter, Not Harder
munetoshi
0
150
Railsアプリケーションと パフォーマンスチューニング ー 秒間5万リクエストの モバイルオーダーシステムを支える事例 ー Rubyセミナー 大阪
falcon8823
5
1.1k
AI時代のソフトウェア開発を考える(2025/07版) / Agentic Software Engineering Findy 2025-07 Edition
twada
PRO
76
25k
Hack Claude Code with Claude Code
choplin
3
890
0626 Findy Product Manager LT Night_高田スライド_speaker deck用
mana_takada
0
160
Code as Context 〜 1にコードで 2にリンタ 34がなくて 5にルール? 〜
yodakeisuke
0
120
設計やレビューに悩んでいるPHPerに贈る、クリーンなオブジェクト設計の指針たち
panda_program
6
2k
効率的な開発手段として VRTを活用する
ishkawa
0
130
チームで開発し事業を加速するための"良い"設計の考え方 @ サポーターズCoLab 2025-07-08
agatan
1
320
Quand Symfony, ApiPlatform, OpenAI et LangChain s'allient pour exploiter vos PDF : de la théorie à la production…
ahmedbhs123
0
150
Kotlin エンジニアへ送る:Swift 案件に参加させられる日に備えて~似てるけど色々違う Swift の仕様 / from Kotlin to Swift
lovee
1
260
Featured
See All Featured
The Invisible Side of Design
smashingmag
301
51k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Balancing Empowerment & Direction
lara
1
420
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
161
15k
Raft: Consensus for Rubyists
vanstee
140
7k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.8k
Designing for humans not robots
tammielis
253
25k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
26k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.5k
The World Runs on Bad Software
bkeepers
PRO
69
11k
Visualization
eitanlees
146
16k
Code Reviewing Like a Champion
maltzj
524
40k
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