>If it had py26 classifiers, that was an error. The list of libraries with py26 classifiers is too huge: astara - stable/kilo, stable/liberty astara-appliance - stable/kilo, stable/liberty astara-horizon - stable/kilo, stable/liberty astara-neutron - stable/kilo, stable/liberty bifrost - stable/liberty ceilometermiddleware - stable/kilo, stable/liberty cloudkitty-dashboard - stable/kilo compute-hyperv - stable/kilo, stable/liberty congress - stable/kilo, stable/liberty debtcollector - stable/kilo, stable/liberty designate - stable/kilo, stable/liberty designate-dashboard - stable/liberty glance_store - stable/kilo group-based-policy - stable/kilo group-based-policy-automation - stable/kilo group-based-policy-ui - stable/kilo instack-undercloud - stable/liberty keystoneauth - stable/liberty keystonemiddleware - stable/kilo magnum - stable/kilo, stable/liberty magnum-ui - stable/liberty manila-ui - stable/kilo, stable/liberty mox3 - stable/liberty networking-bagpipe - stable/kilo, stable/liberty networking-bgpvpn - stable/kilo, stable/liberty networking-hyperv - stable/kilo, stable/liberty networking-infoblox - stable/liberty networking-l2gw - stable/kilo, stable/liberty networking-nec - stable/kilo networking-ovs-dpdk - stable/kilo, stable/liberty networking-plumgrid - stable/kilo, stable/liberty networking-vsphere - stable/kilo, stable/liberty nova-docker - stable/kilo, stable/liberty nova-solver-scheduler - stable/kilo os-brick - stable/liberty os-client-config - stable/liberty oslo-incubator - stable/kilo oslo.cache - stable/liberty oslo.concurrency - stable/kilo, stable/liberty oslo.config - stable/kilo, stable/liberty oslo.context - stable/kilo, stable/liberty oslo.db - stable/kilo, stable/liberty oslo.i18n - stable/kilo, stable/liberty oslo.log - stable/kilo, stable/liberty oslo.messaging - stable/kilo oslo.middleware - stable/kilo, stable/liberty oslo.policy - stable/kilo, stable/liberty oslo.reports - stable/liberty oslo.rootwrap - stable/kilo, stable/liberty oslo.serialization - stable/kilo, stable/liberty oslo.service - stable/liberty oslo.utils - stable/kilo, stable/liberty oslo.versionedobjects - stable/kilo oslo.vmware - stable/kilo, stable/liberty oslosphinx - stable/kilo, stable/liberty oslotest - stable/kilo, stable/liberty pycadf - stable/kilo, stable/liberty python-barbicanclient - stable/kilo, stable/liberty python-ceilometerclient - stable/kilo, stable/liberty python-cinderclient - stable/kilo, stable/liberty python-congressclient - stable/kilo, stable/liberty python-designateclient - stable/kilo, stable/liberty python-glanceclient - stable/kilo, stable/liberty python-group-based-policy-client - stable/kilo python-heatclient - stable/kilo, stable/liberty python-ironicclient - stable/kilo, stable/liberty python-keystoneclient - stable/kilo, stable/liberty python-magnumclient - stable/kilo, stable/liberty python-neutronclient - stable/kilo, stable/liberty python-novaclient - stable/kilo, stable/liberty python-openstackclient - stable/kilo, stable/liberty python-saharaclient - stable/kilo, stable/liberty python-swiftclient - stable/kilo, stable/liberty python-tackerclient - stable/kilo, stable/liberty python-troveclient - stable/kilo, stable/liberty python-zaqarclient - stable/kilo, stable/liberty requirements - stable/kilo, stable/liberty stevedore - stable/liberty swift - stable/kilo tacker - stable/kilo, stable/liberty tacker-horizon - stable/kilo, stable/liberty taskflow - stable/kilo tooz - stable/kilo tripleo-common - stable/liberty yaql - stable/kilo, stable/liberty zaqar - stable/kilo, stable/liberty
On Wed, Dec 16, 2015 at 1:52 PM, Andreas Jaeger <[email protected]> wrote: > On 2015-12-16 12:33, Andrey Kurilin wrote: > >> Hi all, >> As you may know, support of Python 2.6 was dropped this month from most >> of OpenStack projects. Also infrastructure team dropped Centos 6.x jobs. >> >> I'm ok with dropping Python 2.6 support from the master(Mitaka), but >> what about stable/kilo and stable/liberty ? Kilo and Liberty were >> released with Python 2.6 support and most of projects have py26 >> classifiers there. Without py26 jobs in stable branches, it is hard to >> backport any changes. >> > > Kilo and liberty was not released and neither tested on our server > projects for Python 2.6. If it had py26 classifiers, that was an error. > > It was tested only on the client projects so that new python client > libraries could connect to an older installation. > > Andreas > > Also, requirements for stable/liberty do not contain upper caps for >> python-*clients and oslo.* libraries, so most of projects already have >> broken py26 support in Liberty. >> >> -- >> Best regards, >> Andrey Kurilin. >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > -- > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Best regards, Andrey Kurilin.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
