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
ペアプロ × 生成AI 現場での実践と課題について / generative-ai-in-pair-programming
codmoninc
2
20k
技術同人誌をMCP Serverにしてみた
74th
1
680
20250628_非エンジニアがバイブコーディングしてみた
ponponmikankan
0
710
Advanced Micro Frontends: Multi Version/ Framework Scenarios @WAD 2025, Berlin
manfredsteyer
PRO
0
340
顧客の画像データをテラバイト単位で配信する 画像サーバを WebP にした際に起こった課題と その対応策 ~継続的な取り組みを添えて~
takutakahashi
1
150
PHP 8.4の新機能「プロパティフック」から学ぶオブジェクト指向設計とリスコフの置換原則
kentaroutakeda
2
990
チームのテスト力を総合的に鍛えて品質、スピード、レジリエンスを共立させる/Testing approach that improves quality, speed, and resilience
goyoki
5
990
AIエージェントはこう育てる - GitHub Copilot Agentとチームの共進化サイクル
koboriakira
0
610
Composerが「依存解決」のためにどんな工夫をしているか #phpcon
o0h
PRO
1
320
Startups on Rails in Past, Present and Future–Irina Nazarova, RailsConf 2025
irinanazarova
0
150
なぜ適用するか、移行して理解するClean Architecture 〜構造を超えて設計を継承する〜 / Why Apply, Migrate and Understand Clean Architecture - Inherit Design Beyond Structure
seike460
PRO
3
780
AI時代の『改訂新版 良いコード/悪いコードで学ぶ設計入門』 / ai-good-code-bad-code
minodriven
21
8.7k
Featured
See All Featured
Making the Leap to Tech Lead
cromwellryan
134
9.4k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
331
22k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
46
9.6k
Rebuilding a faster, lazier Slack
samanthasiow
83
9.1k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
45
7.5k
How to train your dragon (web standard)
notwaldorf
96
6.1k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.9k
Testing 201, or: Great Expectations
jmmastey
43
7.6k
Statistics for Hackers
jakevdp
799
220k
Why You Should Never Use an ORM
jnunemaker
PRO
58
9.4k
Java REST API Framework Comparison - PWX 2021
mraible
31
8.7k
Build The Right Thing And Hit Your Dates
maggiecrowley
36
2.8k
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