[python-committers] Pace of change for Python 3.x

[Eric V. Smith]

On 1/25/2017 7:30 AM, Antoine Pitrou wrote:
>> We'd just say:
>> this is our new LTS release (e.g. Python 3.7) and then move on
>> until we're confident again that the feature set has stabilized
>> enough to create a new LTS release.
>
> In practice you wouldn't just "move on" but have to maintain that LTS
> release (which is the whole point).  If we're talking something past the
> 2 years timerange, you can't just impose that on all core developers, so
> you need a subgroup of maintainers dedicated to that LTS release.

Channeling Nick, I'd say that LTS support should come from commercial 
third parties, such as OS vendors. I agree with Antoine: it's not 
something we want to impose on the core devs. How much fun is 2.7 
maintenance?

Eric.