On 01/03/2014 08:27 PM, Robert Collins wrote:
On 4 January 2014 08:44, Doug Hellmann wrote:
It seems safer to gate changes to libraries against the apps' trunk (to
avoid making backwards-incompatible changes), and then gate changes to the
apps against the released libraries (to ensure they work
On 01/03/2014 12:09 PM, James E. Blair wrote:
Sean Dague writes:
So my feeling is we should move away from the point graphs we have,
and present these as weekly and daily failure rates (with graphs and
error bars). And slice those per job. My suggestion is that we do the
actual visualization w
Sean,
Before everything, I'd like to thank you for insisting in making the
transition to SQLA 0.8.x.
Since it has been uploaded to Sid, this SQLA <0.7.99 has been without
any doubt the biggest reoccurring pain in the but with the packaging of
OpenStack. Without people like you, insisting again an
On 01/04/2014 06:10 AM, Ivan Melnikov wrote:
> On 04.01.2014 01:29, Sean Dague wrote:
>> On 01/03/2014 04:17 PM, Doug Hellmann wrote:
> [...]
>>> That's what made me think of the solution. But isn't setuptools in fact
>>> telling us that somehow the versions of things we expected to have
>>> instal
On 01/04/2014 07:53 AM, Joshua Harlow wrote:
> So another idea that was talked about on IRC.
>
> Taskflow exposes entrypoints for these storage backends (like your storage
> callback/interface idea).
>
> It currently provides 3 such 'default' backends [sqlalchemy, file/dir
> based, in-memory <-->
Such a bad state seems like FUD.
Taskflow was just syncing its requirements with the same requirements that
everyone else is... Those global requirements have <0.7.99 in them as we speak
(which is why taskflow picked up that version).
The issue here will be worked through and fixed, it won't b
On 01/05/2014 12:12 AM, Joshua Harlow wrote:
> it won't
> be the last time a library that is used in various projects
> causes dependency issues
Please, tell me the opposite thing. Please tell me that this is the last
time we're having a discussion about problems with SQLA 0.8. Please tell
me that
I was more of referring to general dependency issues, sqlalchemy hopefully
never again but one never knows :P
Sent from my really tiny device...
> On Jan 4, 2014, at 8:40 AM, "Thomas Goirand" wrote:
>
>> On 01/05/2014 12:12 AM, Joshua Harlow wrote:
>> it won't
>> be the last time a library tha
Folks,
I finally got over my fear of weather and booked my flight and hotel for
this sprint.
I am relatively new to OpenStack community with a strong desire to learn
and contribute.
You may have seen that "Arista Testing" has come alive and is voting on the
newly submitted neutron patches. I hav
Hi all,
I'm testing the Havana devstack and I noticed that after killing and
restarting the neutron server public networks are not returned when
queried via horizon or command line, which in Grizzly devstack the query
returns the external network even after a quantum-server restart:
Basically
On 5 January 2014 04:22, Thomas Goirand wrote:
> Sean,
>
> Before everything, I'd like to thank you for insisting in making the
> transition to SQLA 0.8.x.
>
> Since it has been uploaded to Sid, this SQLA <0.7.99 has been without
> any doubt the biggest reoccurring pain in the but with the packagi
11 matches
Mail list logo
