According to securityspace's October-November delta, nearly half a million
web hosts jumped to httpd 2.2.31 in the past month alone (almost entirely
from older 2.2.x servers) while 11k downgraded to an older 2.2 or upgraded
2.2.31 to 2.4.x.

Half a million in 31 days?  This is triple the 2.2.31 adoption from the
Sept time-frame.

http://www.securityspace.com/s_survey/data/man.201510/srvch.html?server=Apache&revision=Apache%2F2.2.31

The httpd 2.4.12 - 2.4.17 series experienced about 142k upgrades vs. 16k
downgrades over the same period, and similar numbers in Sept-Oct.  Those
releases are essentially concurrent with the 2.2.31 release, and I didn't
look back into 2014's releases on either branch since 2.2.29 and 2.4.10 are
both over a year old.

Here are some tallies to give you a rough idea of what happened last month;
FromToFromTo2.2.x-2.2.314723592.2.312.4.x26972.4.x+2.2.3119162.2.312.2.x-
1634Other2.2.31246702.2.31Other6697498945110282.4.x-2.4.x613082.4.x2.4.x-800
2.2.x2.4.x419742.4.x2.2.x-2715Other2.4.x385992.4.xOther1238114188115896
Upgrades640826Downgrades26924

2.4.x refers to the 2.4.12 - 2.4.17 releases (past 12 mos,
the same basic lifespan as 2.2.31), but I tallied our earlier
2.4.x release counts for any +/- upgrade/downgrade deltas.
E.g. 2.2.4 -> 2.4.7 isn't counted anywhere, but 2.4.16 -> 2.4.7
is counted as a 2.4.x- downgrade.  I counted 2.4.12 -> 2.4.16
only once, in the 2.4.x+ upgrade tally.

2.2.x refers to 2.2 flavors prior to 2.2.31, but .31 is tallied
but I tallied 2.2.31 into +/- upgrade/downgrade deltas.
I did re-count 2.4.x+ -> 2.2.31 conversion in the 2.4.x -> 2.2.x-
downgrade tally.

"Other" may be pre-2.4.x, or a non-specific Apache/2 Server string,
or too small a proportion to call out individually.

On the one hand, I'm ecstatic that users are clearly upgrading at
maybe the fastest pace in forever.  On the other hand, I am stuck
wondering how we have made the 2.4.x transition effectively 3x
harder than upgrading within the 2.2 lineage, and puzzling over
what we can improve as a project to ease this transition for millions
of deployed 2.2.x instances.

Reply via email to