10 Distributions
206,404 Total Packages
4,734,131 Releases
3,239 Upstream Packages
Current Releases
Rank Distro Codename % Obsolete Avg # New Rels Avg Lag
1 arch 27.27% 1.70 1w
2 fedora 20 61.29% 3.42 12w
3 gentoo 66.66% 10.70 22w
4 funtoo 66.66% 10.79 23w
5 ubuntu trusty 69.69% 7.06 12w
6 sabayon 5 69.69% 21.91 28w
7 debian wheezy 81.81% 23.82 79w
8 slackware 14.1 84.21% 12.68 34w
9 opensuse 13.1 87.5% 11.22 34w
10 freebsd 9.2 90.0% 57.63 92w
Future Releases
Rank Distro Codename % Obsolete Avg # New Rels Avg Lag
1 arch 27.27% 1.70 1w
2 debian jessie 36.36% 6.30 8w
3 gentoo 36.36% 1.48 2w
4 funtoo 36.36% 1.48 2w
5 opensuse 13.1 37.5% 3.81 9w
6 ubuntu utopic 42.42% 7.76 15w
7 fedora 21 64.51% 3.52 13w
8 sabayon 5 69.69% 21.85 26w
9 slackware current 78.94% 5.21 24w
10 freebsd 9 89.65% 61.45 75w
What
If Subversion's latest releases are:
03/20/09 1.6.0
02/27/09 1.5.6
12/22/08 1.5.5
10/24/08 1.5.4

And say gentoo stable is at 1.5.5 on 03/23/09.

Then the lag is 3/23/09-2/27/09, the time between now and the oldest new release.

Thus, the lag is 24 days.
Much of the analysis of the gathered data is centered around a notion of downstream lag. That is, for any given point in time a distribution's package version lags behind by the time difference between now and the oldest new release.

Around the site you will find many graphs that display the downstream lag over time. Most average the lag over a number of packages to gather a greater sense of a distribution's tendencies.
About
OpenSourceWatershed is a project aimed at understanding the relationship between distributions (downstream) and the individual software components (upstream). It is the basis for a larger study of distributions and their evolution. It is distrology.

The aggregate analysis is done over a variety of packages. The three forms of analysis are percent obsolete, the average number of newer releases per package and the time since the oldest new release. In other words the lag is the amount of time a distro had to move to a newer package.

There are errors in the database which you can help fix. Just email the mailing list if you find one. Join the GoogleGroup to get notified of improvements to the site. Individual packages can be tracked using RSS feeds by clicking the feed icon next to each package name. For more information about the process behind this analysis please read my senior thesis or email me.

©2013 Scott Shawcroft | CC-by 3.0 US - contact - git - changes - list