Interesting, Francesco - thanks for putting this together.
I believe there was community feedback to the core team around 2.0 requesting that they slow the pace of major point releases (ie 2.1, 2.2) in order to reduce admin workload installing updates. Beginning in 2.0 each tarball received a proper minor release number (eg 2.0.1) whereas before they just got the repository version number.
FWIW, here are the number of minor point releases tagged in the svn repository:
1 Comment
Hide/Show CommentsSep 22, 2009
JoeMurray
Interesting, Francesco - thanks for putting this together.
I believe there was community feedback to the core team around 2.0 requesting that they slow the pace of major point releases (ie 2.1, 2.2) in order to reduce admin workload installing updates. Beginning in 2.0 each tarball received a proper minor release number (eg 2.0.1) whereas before they just got the repository version number.
FWIW, here are the number of minor point releases tagged in the svn repository:
Release
Number of stable minor point releases / tarballs
Number of Alpha release
Number of Beta releases
1.6
14
3
4
1.7
4
4
8
1.8
4
2
4
1.9
8
1
2
2.0
8
4
5
2.1
7
4
6
2.2
10
3
4
3.0
3
4