On 08/18/2015 09:34 PM, John Griffith wrote:
On Tue, Aug 18, 2015 at 7:42 PM, John Griffith john.griffi...@gmail.com
mailto:john.griffi...@gmail.com wrote:
On Tue, Aug 18, 2015 at 2:14 PM, Robert Collins
robe...@robertcollins.net mailto:robe...@robertcollins.net wrote:
On 20 August 2015 at 01:42, Sean Dague s...@dague.net wrote:
Sorry about jumping the gun there. We thought, incorrectly, we had the
right fix. And it's a conference week so access to my local test env
wasn't easy.
No worries - these things happen. Having higher fidelity tests would
give some
On Tue, Aug 18, 2015 at 7:42 PM, John Griffith john.griffi...@gmail.com
wrote:
On Tue, Aug 18, 2015 at 2:14 PM, Robert Collins robe...@robertcollins.net
wrote:
On 19 August 2015 at 03:51, Sean Dague s...@dague.net wrote:
So... I'm at Linux Con this week, meaning that things will be
On 19 August 2015 at 03:51, Sean Dague s...@dague.net wrote:
So... I'm at Linux Con this week, meaning that things will be slow. I
think - https://review.openstack.org/#/c/208582/ (slightly updated this
morning) will get devstack users working again. And I agree, we really
need devstack and
On Tue, Aug 18, 2015 at 2:14 PM, Robert Collins robe...@robertcollins.net
wrote:
On 19 August 2015 at 03:51, Sean Dague s...@dague.net wrote:
So... I'm at Linux Con this week, meaning that things will be slow. I
think - https://review.openstack.org/#/c/208582/ (slightly updated this
On 08/14/2015 02:52 AM, Chris Dent wrote:
On Fri, 14 Aug 2015, Clint Byrum wrote:
The same is true for these bugs. Yes they're real, yes more orgs should
devote developers to fixing them.
This may be the root of my concern and something that we're going to
have to address sooner than
On 17 August 2015 at 20:45, Jesse Pretorius jesse.pretor...@gmail.com wrote:
Do we want to make it a default to True for users of DevStack? I think
it
may be worth considering since I'm not familiar with this issue with
crypto
and having something that protects devs who are trying to
Do we want to make it a default to True for users of DevStack? I think it
may be worth considering since I'm not familiar with this issue with
crypto
and having something that protects devs who are trying to work on stuff
and
using DevStack , sounds good. Less cryptic day to day
On Fri, 14 Aug 2015, Robert Collins wrote:
The vast majority of our developers do not fix such bugs. They react
by blacklisting the proximate cause of the issue - the new release -
locally, submit a patch to openstack/requirements *sometimes* and if
we're really lucky file a bug upstream.
Excerpts from Chris Dent's message of 2015-08-14 02:08:28 -0700:
On Fri, 14 Aug 2015, Robert Collins wrote:
The vast majority of our developers do not fix such bugs. They react
by blacklisting the proximate cause of the issue - the new release -
locally, submit a patch to
On 14 August 2015 at 21:08, Chris Dent chd...@redhat.com wrote:
Awesome, thanks for pointing this out, that will be useful.
But again: Underlying my assertion is that we don't _just_ need more
tools and automation we also need to remind ourselves of the kind of
environment that we're
On Thu, 13 Aug 2015, Sean M. Collins wrote:
Do we want to make it a default to True for users of DevStack? I think
it may be worth considering since I'm not familiar with this issue
with crypto and having something that protects devs who are trying to
work on stuff and using DevStack , sounds
On 14 August 2015 at 20:31, Chris Dent chd...@redhat.com wrote:
On Thu, 13 Aug 2015, Sean M. Collins wrote:
Do we want to make it a default to True for users of DevStack? I think
it may be worth considering since I'm not familiar with this issue
with crypto and having something that protects
On Fri, 14 Aug 2015, Clint Byrum wrote:
The same is true for these bugs. Yes they're real, yes more orgs should
devote developers to fixing them.
This may be the root of my concern and something that we're going to
have to address sooner than later.
Your concerns are valid and appreciated.
tl;dr - developers running devstack probably want to be using
USE_CONSTRAINTS=True, otherwise there may be a few rough hours today.
[http://lists.openstack.org/pipermail/openstack-dev/2015-July/068569.html]
Apparently some third party CI systems are seeing an issue with
cryptography 1.0 -
On 14 August 2015 at 11:05, Sean M. Collins s...@coreitpro.com wrote:
On August 13, 2015 3:45:03 AM EDT, Robert Collins
robe...@robertcollins.net wrote:
tl;dr - developers running devstack probably want to be using
USE_CONSTRAINTS=True, otherwise there may be a few rough hours today.
On August 13, 2015 3:45:03 AM EDT, Robert Collins robe...@robertcollins.net
wrote:
tl;dr - developers running devstack probably want to be using
USE_CONSTRAINTS=True, otherwise there may be a few rough hours today.
[http://lists.openstack.org/pipermail/openstack-dev/2015-July/068569.html]
17 matches
Mail list logo
