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
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
180
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
思考垂れ流し開発 ~音声入力 × AIエージェント × 開発ハーネスによる試行錯誤~
npostring
0
120
Detecting Compromised CI with eBPF and Cilium Tetragon
lizrice
0
250
VibeCodingからAgenticWorkflowへ
starfish719
0
790
AWS DevOps AgentのAzure接続機能を検証して見えた活用法/Use Cases Verified for the AWS DevOps Agent's Azure Connectivity Feature
masakiokuda
1
270
TSX の <Hoge<Fuga>> という構文に驚いた話 / tsx-type-argument-syntax
kanaru0928
0
240
自動化したのに回らない テスト運用の壁―AI時代の品質責任と生産性
mfunaki
0
430
Japan Community Day at Kubecon + CloudNativeCon Japan 2026: Learning Container Privilege Control by Building My Own Low-Level Container Runtime
ternbusty
1
170
レビュー履歴をAIに食わせて、 Compose移行を加速するs
shihochan
0
200
仕様駆動開発の消費期限
watany
20
8.9k
生成AIで帳票OCRが「簡単に」作れる時代になった?
kon_shou
0
1.2k
コンパウンドプロダクト開発のためのローカルプロセスマネージャー再発明 #layerxgo
izumin5210
0
190
Webエンジニアなのにブラウザの仕組みがわからないので、Pythonで自作してみた
tatsuki12
4
1k
Featured
See All Featured
We Have a Design System, Now What?
morganepeng
55
8.3k
Fashionably flexible responsive web design (full day workshop)
malarkey
408
67k
Sam Torres - BigQuery for SEOs
techseoconnect
PRO
0
500
HDC tutorial
michielstock
2
810
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
How to train your dragon (web standard)
notwaldorf
97
6.8k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
21
1.6k
DBのスキルで生き残る技術 - AI時代におけるテーブル設計の勘所
soudai
PRO
68
57k
The Pragmatic Product Professional
lauravandoore
37
7.4k
Agile that works and the tools we love
rasmusluckow
331
22k
State of Search Keynote: SEO is Dead Long Live SEO
ryanjones
0
250
Introduction to Domain-Driven Design and Collaborative software design
baasie
1
950
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