2.1.8 and 2.2.0

[Alan Buxey]

Hi,

> 
>   The question then is, do we want to have BOTH:
> 
> 2.1.8 = 2.1.7 + bug fixes ONLY
> 
> 2.2.0 = major new features + any fixes
> 
>   OR, do we want to give up on 2.1.8, and just release 2.2.0?
> 
>   There are pros and cons both ways.  Having a stable 2.1.8 is good.
> But maintaining two versions could confuse people.

we already have 2 versions that people get confused and want support on..

1.x and 2.x  (in fact, you could say 1.0.x, 1.1.x, 2.0.x and 2.1.x ! :-) )


however, i would be happy to have 2.1.8 and 2.2.0 for the short term - because
2.1.x train is one that everyone is familiar with and works in the 2.1.x way
where-as - as you say, 2.2.x will have new features, methods etc - it would
make sense , then to say 2.1.8 for the small upgraders and 2.2.x for those wanting
the new features/methods etc.   ..and can we say goodbye to all 1.x 'support' ? :-)

alan