10 Distributions
223,942 Total Packages
5,283,589 Releases
3,304 Upstream Packages
Current Releases
Rank Distro Codename % Latest Avg # Newer Rels Avg Lag
1 gentoo 31.25% 9.78 33w
2 funtoo 31.25% 9.78 33w
3 ubuntu vivid 28.12% 8.56 14w
4 debian jessie 25.0% 8.53 31w
5 arch 25.0% 13.31 13w
6 freebsd 10.1 23.33% 35.60 86w
7 sabayon 5 21.87% 10.41 39w
8 fedora 22 16.66% 5.13 17w
9 slackware 14.1 10.52% 11.68 62w
10 opensuse 13.1 6.45% 11.55 64w
Future Releases
Rank Distro Codename % Latest Avg # Newer Rels Avg Lag
1 gentoo 62.5% 2.09 12w
2 funtoo 62.5% 2.09 12w
3 opensuse 13.2 59.37% 3.00 13w
4 slackware current 57.89% 1.79 4w
5 ubuntu wily 37.5% 10.41 25w
6 debian stretch 34.37% 3.91 20w
7 arch 25.0% 13.31 13w
8 freebsd 10.1 24.13% 34.69 68w
9 sabayon 5 21.87% 10.31 36w
10 fedora 23 16.66% 5.13 17w
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 latest, 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