+1 from me as well.
2015년 7월 10일 (금) 18:27, Neil Jerram 님이 작성:
> On 10/07/15 10:19, Thierry Carrez wrote:
> >
> > Part of the confusion here is that we are not naming "releases". We are
> > naming release *cycles*. We are giving a name to a period of time,
> > basically. In that period of time, v
+1 for this.
On Fri, Jul 10, 2015 at 5:20 PM Thierry Carrez
wrote:
> Adam Lawson wrote:
> > The alternative of course is to just number the releases since names
> > ultimately don't mean anything but it seems there are problems with that
> > level of simplicity. I personally prefer Tristan's sug
+1 for this
On Fri, Jul 10, 2015 at 5:20 PM Thierry Carrez
wrote:
> Adam Lawson wrote:
> > The alternative of course is to just number the releases since names
> > ultimately don't mean anything but it seems there are problems with that
> > level of simplicity. I personally prefer Tristan's sugg
Just a correction of what I stated earlier...
- Original Message -
> From: "Csaba Henk"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Thursday, July 9, 2015 3:13:29 PM
> Subject: Re: [openstack-dev] [manila] share dismantling policies
...
> Sure, Manila
On 11 July 2015 at 15:54, Ian Cordasco wrote:
> On 7/10/15, 18:34, "Monty Taylor" wrote:
>
>>On 07/10/2015 07:19 PM, Robert Collins wrote:
>>> On 10 July 2015 at 01:59, Morgan Fainberg
>>>wrote:
Or a database per python major version (or at least gracefully handle
the incompatibility).
On 11 July 2015 at 12:38, Matthew Treinish wrote:
> On Sat, Jul 11, 2015 at 11:35:16AM +1200, Robert Collins wrote:
>> On 9 July 2015 at 10:52, Jeremy Stanley wrote:
>> > On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote:
>> >> So - I'm looking to:
>> >>
>> >> A) have a discussion and id
On 11 July 2015 at 22:04, Robert Collins wrote:
> On 11 July 2015 at 12:38, Matthew Treinish wrote:
>> The whole argument for making testr live outside of the venv and being an
>> implicit dependency like tox is based around tracking the results between the
>> tox venvs right? If we decoupled th
@sdague, @lifeless, requirements-core folks,
Looks like we still need this requirements review to merge to help fix
a bunch of oslo library failures:
https://review.openstack.org/#/c/200344/
Thanks,
dims
On Fri, Jul 10, 2015 at 6:55 PM, Robert Collins
wrote:
> On 11 July 2015 at 04:50, Jeremy S
Hi all,
After running ./stack.sh
I am getting the following error.
015-07-11 17:01:02.188 | error in setup command: 'tests_require' must
be a string or list of strings containing valid project/version requirement
specifiers; Expected ',' or end-of-list in
python-ldap>=2.4;python_version=='2.
Thierry,
Well put, and interesting. I didn't know about the other cultural concerns
around numbers.
Most importantly, I think using names for releases is better than numbers,
creating a more personal connection to each release. Would hate to see that
end.
Unfortunately there isn't much we can do
On 2015-07-11 22:49:27 +0530 (+0530), Venkateswarlu P wrote:
> After running ./stack.sh
> I am getting the following error.
>
> 015-07-11 17:01:02.188 | error in setup command: 'tests_require' must
> be a string or list of strings containing valid project/version requirement
> specifiers; Expe
On 2015-07-11 18:09:26 + (+), Jeremy Stanley wrote:
> On 2015-07-11 22:49:27 +0530 (+0530), Venkateswarlu P wrote:
> > After running ./stack.sh
> > I am getting the following error.
> >
> > 015-07-11 17:01:02.188 | error in setup command: 'tests_require' must
> > be a string or list of
On 7/10/15, 03:44, "Thierry Carrez" wrote:
>Joshua Harlow wrote:
>> Hi all,
>>
>> I was thinking about those who are packaging with venvs (and using the
>> version of a project in the venv file name); like what anvil[1] is now
>> capable of (and does this in the gate now[2]) or packaging via r
Ian Cordasco wrote:
On 7/10/15, 03:44, "Thierry Carrez" wrote:
Joshua Harlow wrote:
Hi all,
I was thinking about those who are packaging with venvs (and using the
version of a project in the venv file name); like what anvil[1] is now
capable of (and does this in the gate now[2]) or packagin
Just wanted to clarify if a normal PCI device (instead of a VF) can be attached
to the neutron port when using the SR-IOV networking as described in
https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking. If it is not
supported just wondering if there is already a blueprint.
Cheers,
-
Hello,
in my tox.inienvlist = py27,pep8,docs,genconfig
my tox runs ok.
why so many failure occured in jekins.
Would you please tell me?
This the first time for me to commit patch.__
OpenStack Development Mailing List (no
Hi @jiaxi,
please see failures caused by the code change in your patch :) Hope that helps.
http://logs.openstack.org/12/200512/5/check/gate-tempest-dsvm-large-ops/a2bcf0c/logs/devstacklog.txt.gz#_2015-07-11_16_32_56_433
http://logs.openstack.org/12/200512/5/check/gate-tempest-dsvm-large-ops/a2bcf
Hey,
Yes, sorry, I only discovered this yesterday. I should have updated the
wiki page sooner but I've placed some details there now:
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo+topic:fix-th,n,z
Basically the removal of migrate-flavor-data from master br
18 matches
Mail list logo
