You are not logged in.
Pages: 1
Topic closed
From Slashdot:
http://linux.slashdot.org/story/09/07/2 … art_pos=20
---
"Linux distributions track upstream projects, releasing a particular version with each official release. But how far behind the latest versions do these releases linger? Scott Shawcroft did an interesting new study into this relationship between distributions and upstream projects. Shawcroft says: 'Over the last 10 months I've been working on Linux evolution research. Similar to distrowatch, I track the current versions of packages in a number of distributions and the current upstream version. Based on that data I then graph a number of metrics to understand the relationship between upstream and downstream.' His presentation on the topic scheduled for [this] week's open source convention, OSCON, should provide an interesting insight into that relationship. Currently he is tracking 20 projects including the Linux kernel, Firefox, GCC, OpenSSH and GNOME on Arch, Debian, Fedora, Gentoo, openSUSE, Sabayon, Slackware, and Ubuntu."
http://tannewt.org/slides/shawcroft-osc … tation.pdf
---
(See Page 12 of the pdf)
Arch has, by far, the shortest delay from upstream source release to distro incorporation. I think that says a lot about the idea of a rolling release system; while other distributions have delays measured in months (or years, in the case of Debian), the downstream propagation delay is measured in days/weeks for Arch Linux.
![]()
Altrus
Offline
You're only 12 hours late to the party ![]()
Offline
Offline
duplicate thread. closing.
Offline
Pages: 1
Topic closed