Open Stack

Andreas,

Totally understand the overload problem with no short-term workarounds.  I
think all engineering in OpenStack is over capacity a bit and folks are
really burning the midnight oil to make sure Mitaka is the best release of
OpenStack yet!

Please feel free to drop by #kolla and ping the core reviewers if you need
any help getting this work reverted until the timing is better.

Regards
-steve


On 2/11/16, 1:50 AM, "Andreas Jaeger" <aj at suse.com> wrote:

>On 2016-02-11 02:50, Joshua Hesketh wrote:
>> Hey Andreas,
>> 
>> Why not keep pep8 as an alias for the new linters target? Would this
>> allow for a transition path while work on updating the PTI is done?
>
>pep8 and linters do different work in infra, and infra calls pep8. A
>project can have both...
>
>It's more than updating PTI, it's also taking care that linters does the
>same tests as pep8 and then updating *all* projects...
>
>Andreas
>
>> Cheers,
>> Josh
>> 
>> On Thu, Feb 11, 2016 at 6:55 AM, Andreas Jaeger <aj at suse.com
>> <mailto:aj at suse.com>> wrote:
>> 
>>     Hi,
>> 
>>     the pep8 target is our usual target to include style and lint
>>checks and
>>     thus is used besides pep8 also for doc8, bashate, bandit, etc as
>>     documented in the PTI (=Python Test Interface,
>>     http://governance.openstack.org/reference/cti/python_cti.html).
>> 
>>     We've had some discussions to introduce a new target called linters
>>as
>>     better name for this and when I mentioned this in a few
>>discussions, it
>>     resonated with these projects. Unfortunately, I missed the
>>relevance of
>>     the PTI for such a change - and changing the PTI to replace pep8
>>with
>>     linters and then pushing that one through to all projects is more
>>than I
>>     can commit to right now.
>> 
>>     I apologize for being a too eager and will send patches for official
>>     projects moving them back to pep8, so consider this is heads up and
>>     background about my incoming patches with topic "pti-pep8-linters".
>> 
>>     If somebody else wants to do the whole conversion in the future, I
>>can
>>     give pointers on what to do,
>> 
>>     Andreas
>>     --
>>      Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org
>>     <http://opensuse.org>} Twitter/Identica: 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:
>>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>     
>><http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> 
>> 
>> 
>>_________________________________________________________________________
>>_
>> 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
>> 
>
>
>-- 
> 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: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev