Open Stack

Excerpts from Davanum Srinivas (dims)'s message of 2015-11-16 09:23:39 -0500:
> Gordon,
> 
> When we stop the py26 jobs, the next version we release should have
> major bumps by semver definition. liberty does not have version caps
> unfortunately, but i'll let Doug and others chime in on that.
> 
> yes, i know major bumps are hard

Yes, I would expect major version number increases and trove
classifier updates (in setup.cfg) to indicate that some support has
been dropped. It's simpler to do it now, than to do it at some point
in the future when we introduce a syntactic or standard library
dependency that is not available in 2.6.

The constraints file in liberty should protect us from introducing
versions that are actually incompatible. If we need to go back and add a
few caps, or add environment markers to support different ranges on 2.6
and >=2.7, we can do that as we discover the need.

Doug

> 
> thanks,
> dims
> 
> On Mon, Nov 16, 2015 at 9:07 AM, gord chung <gord at live.ca> wrote:
> > do we require a major versioning bump for this? i'm wondering how 'breaking'
> > this is in real life if all the services have dropped py2.6 already. maybe
> > this just requires an upper-cap in appropriate stable branches?
> >
> > to be devils advocate, one (arguably terrible) reason for not doing a major
> > bump is that a lot of libs just did one for the Mitaka cycle.
> >
> > On 11/11/2015 2:14 PM, Davanum Srinivas wrote:
> >>
> >> Folks,
> >>
> >> Any concerns? please chime in:
> >> https://review.openstack.org/244275
> >>
> >> Thanks
> >> -- Dims
> >>
> >
> > --
> > gord
> >
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>