Your thought seems to be that we "EOL" 2.2 when the number of 2.2 deployments < the number of 2.4 ones. My thought is that we "EOL" 2.2 in order to *hasten* that event, just like just about every other open-source and non-open source software project out there.
- Re: 2.2 and 2.4 and 2.6/3.0 Jeff Trawick
- Re: 2.2 and 2.4 and 2.6/3.0 Mike Rumph
- Re: 2.2 and 2.4 and 2.6/3.0 Ivan Zhakov
- Re: 2.2 and 2.4 and 2.6/3.0 Yann Ylavic
- Re: 2.2 and 2.4 and 2.6/3.0 Jim Jagielski
- Re: 2.2 and 2.4 and 2.6/3.0 William A Rowe Jr
- Re: 2.2 and 2.4 and 2.6/3.0 Jim Jagielski
- Re: 2.2 and 2.4 and 2.6/3.0 William A Rowe Jr
- Re: 2.2 and 2.4 and 2.6/3.0 Jim Jagielski
- Re: 2.2 and 2.4 and 2.6/3.0 William A Rowe Jr
- Re: 2.2 and 2.4 and 2.6/3.0 Jim Jagielski
- Re: 2.2 and 2.4 and 2.6/3.0 William A Rowe Jr
- RE: 2.2 and 2.4 and 2.6/3.0 Houser, Rick
- Re: 2.2 and 2.4 and 2.6/3.0 William A Rowe Jr
- Re: 2.2 and 2.4 and 2.6/3.0 Noel Butler
- Re: 2.2 and 2.4 and 2.6/3.0 William A Rowe Jr
- Re: 2.2 and 2.4 and 2.6/3.0 Jim Jagielski
- Re: 2.2 and 2.4 and 2.6/3.0 Jeff Trawick
- Re: 2.2 and 2.4 and 2.6/3.0 Jim Jagielski
- Re: 2.2 and 2.4 and 2.6/3.0 Jeff Trawick
- Re: 2.2 and 2.4 and 2.6/3.0 Jim Jagielski