Stability and change

[James Logajan]

Alex Martelli <aleax at aleax.it> wrote:
> Why don't we start thinking of a similarly dual-tracked Python -- one
> track aiming at stability (in a "middle ground" sensible sense: strong
> commitment to not breaking old code -- introducing small new features
> and new library modules _is_ OK, else one can use a bugfix-only-"track"
> for some previous release), one aiming at frequent releases,
> innovation, etc.

This proposal seems to have good promise and if well executed would 
probably mollify a curmudgeon such as myself.