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
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
usa
May 31, 2018
Programming
0
760
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
160
WindowsにおけるRubyのエンコーディングの話 Ruby3版/Ruby's encoding on Windows at Ruby3
unak
0
460
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.3k
talk about IO
unak
5
2k
Other Decks in Programming
See All in Programming
Railsの気持ちを考えながらコントローラとビューを整頓する/tidying-rails-controllers-and-views-as-rails-think
moro
4
380
CSC307 Lecture 12
javiergs
PRO
0
460
API Platformを活用したPHPによる本格的なWeb API開発 / api-platform-book-intro
ttskch
1
130
受け入れテスト駆動開発(ATDD)×AI駆動開発 AI時代のATDDの取り組み方を考える
kztakasaki
2
550
日本だけで解禁されているアプリ起動の方法
ryunakayama
0
370
Codex の「自走力」を高める
yorifuji
0
1k
猫の手も借りたい!ので AIエージェント猫を作って社内に放した話 Claude Code × Container Lambda の Slack Bot "DevNeko"
naramomi7
0
260
AI駆動開発の本音 〜Claude Code並列開発で見えたエンジニアの新しい役割〜
hisuzuya
4
490
AI時代でも変わらない技術コミュニティの力~10年続く“ゆるい”つながりが生み出す価値
n_takehata
2
670
Go Conference mini in Sendai 2026 : Goに新機能を提案し実装されるまでのフロー徹底解説
yamatoya
0
540
encoding/json/v2のUnmarshalはこう変わった:内部実装で見る設計改善
kurakura0916
0
350
AIに任せる範囲を安全に広げるためにやっていること
fukucheee
0
120
Featured
See All Featured
The Director’s Chair: Orchestrating AI for Truly Effective Learning
tmiket
1
120
How to Get Subject Matter Experts Bought In and Actively Contributing to SEO & PR Initiatives.
livdayseo
0
81
AI: The stuff that nobody shows you
jnunemaker
PRO
3
360
Darren the Foodie - Storyboard
khoart
PRO
3
2.8k
Lightning talk: Run Django tests with GitHub Actions
sabderemane
0
140
Un-Boring Meetings
codingconduct
0
220
The Impact of AI in SEO - AI Overviews June 2024 Edition
aleyda
5
760
Max Prin - Stacking Signals: How International SEO Comes Together (And Falls Apart)
techseoconnect
PRO
0
110
The Hidden Cost of Media on the Web [PixelPalooza 2025]
tammyeverts
2
240
Why Your Marketing Sucks and What You Can Do About It - Sophie Logan
marketingsoph
0
99
Keith and Marios Guide to Fast Websites
keithpitt
413
23k
It's Worth the Effort
3n
188
29k
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