Re:The Linux 2.5, Ruby 1.9 and Python 3 release management a...
by jschwartzi on Tuesday December 27, 2016 @12:09AM
(#13261395)
It's probably all there in their issue trackers. That's partly why software teams track issues, because somewhere there's a decision to be made and a story to be told, and that story is written in the issue before it's closed.
Software development is really all about finishing stories.
It'd be wonderful if their architects collected and codified these somewhere, ie "we did X because of Y, it didn't work, because Z ends up happening"
Mostly as a lesson for the rest of us not to fruitlessly repeat.