Re: [分享] Linux v3.0... 再等等

[guezt ()]

※ 引述《Spig (Spig)》之銘言：
From Linus' google+ message two hours ago,

Linus Torvalds

Why do we always find the subtle bugs just before a release?

Looks like I won't be releasing 3.0 today, just because Hugh found this
incredibly subtle pathname lookup bug. We have a patch, we understand the
problem, and it looks ObviouslyCorrect(tm), but I don't think I want to
release 3.0 just a couple of hours after applying it.

我今天大概不會發布 3.0 了，因為 Hugh 發現了路徑搜尋的小細節出了差錯。
我們有修正檔，也確認了問題，而且看起來明顯是正確的(註), 但我大概不會在
修正這個問題後幾小時內就發布 3.0。

Of course, the bug is so hard to see that Hugh needs weeks to reproduce it
even with his stress test, so we could just ignore it and backport the fix
later. But I really hate making releases with known issues even if it's
almost certainly a "nobody will ever hit this in practice" issue.

當然，這個問題實在太難發現了，即使在 Hugh 的壓力測試下他還是需要花好幾個禮拜
才能重現它，所以我們其實可以就忽略它然後事後再回溯修正這個問題。不過我還是痛恨
發布一個有已知問題的版本，就算幾乎可以確定沒有人實際上會真的遇到這個狀況。

Oh well.

註: ObviouslyCorrect, 意指修正檔(patch)明顯可以有效修正問題，可以馬上加入核心
http://www.tux.org/lkml/#s1-15

--
※ 發信站: 批踢踢實業坊(ptt.cc)
◆ From: 60.248.152.79
→ Adama:第二段 Hugh 的壓力測試 :p
※ 編輯: guezt           來自: 60.248.152.79        (07/19 14:22)
→ guezt:稍微修飾一下句子 :p
→ curist:這篇翻得比較好
→ final01:不是都翻補丁 XD~被同化了嗎
→ uranusjr:ObviouslyCorrent(TM) 其實是個玩笑, 軟體界大家都知道
→ uranusjr:如果把 obviously correct 視為 correct 通常都不會有好
→ uranusjr:下場XD
推 jtmh:原來是這樣，我還特別去 Google ObviouslyCorrent(TM) 到底
→ jtmh:是什麼？結果查不到 XDD
→ guezt:多謝uranusjr補充~
→ guezt:我就不再修文了，如果有什麼暗示或隱喻還請大家指教
※ 編輯: guezt           來自: 122.126.111.184      (07/19 20:21)
→ guezt:自打嘴巴:p 第二段的 High 改成 Hugh (筆誤) m(_ _)m
推 mstar:其實，看到特別加了 (tm) 就知道是大概在開玩笑了 XD
→ mstar:像是玻璃渣的 Soon®  或 Soon™
推 james732:推翻譯
推 kuan:Torvalds本來就蠻喜歡開玩笑，看他的自傳就知道...