On Thu, Aug 28, 2014 at 11:12 PM, Brandon Logan
wrote:
> Kyle,
> Does this apply to blueprints that are destined for the incubator as
> well? I assume the incubator does require a spec process too.
>
Incubator code still requires a spec, yes. For the things which are
incubator candidates, I have
Kyle,
Does this apply to blueprints that are destined for the incubator as
well? I assume the incubator does require a spec process too.
Thanks,
Brandon
On Thu, 2014-08-28 at 08:37 -0500, Kyle Mestery wrote:
> On Thu, Aug 28, 2014 at 8:30 AM, Michael Still wrote:
> > For nova we haven't gotten
> To: Daniel P. Berrange; OpenStack Development Mailing List (not for usage
> questions)
> Subject: Re: [openstack-dev] [nova] [neutron] Specs for K release
>
> On Thu, Aug 28, 2014 at 6:53 AM, Daniel P. Berrange
> wrote:
> > On Thu, Aug 28, 2014 at 11:51:32AM +, Al
d and agreed so we can have this approved and
proceed?
/Alan
-Original Message-
From: Michael Still [mailto:mi...@stillhq.com]
Sent: August-28-14 6:51 PM
To: Daniel P. Berrange; OpenStack Development Mailing List (not for usage
questions)
Subject: Re: [openstack-dev] [nova] [neutron] Specs
+1
I agree that this is a good idea.
Regards,
Mandeep
On Thu, Aug 28, 2014 at 10:13 AM, Jay Pipes wrote:
> On 08/28/2014 12:50 PM, Michael Still wrote:
>
>> On Thu, Aug 28, 2014 at 6:53 AM, Daniel P. Berrange
>> wrote:
>>
>>> On Thu, Aug 28, 2014 at 11:51:32AM +, Alan Kavanagh wro
On 08/28/2014 12:50 PM, Michael Still wrote:
On Thu, Aug 28, 2014 at 6:53 AM, Daniel P. Berrange wrote:
On Thu, Aug 28, 2014 at 11:51:32AM +, Alan Kavanagh wrote:
How to do we handle specs that have slipped through the cracks
and did not make it for Juno?
Rebase the proposal so it is und
On Thu, Aug 28, 2014 at 6:53 AM, Daniel P. Berrange wrote:
> On Thu, Aug 28, 2014 at 11:51:32AM +, Alan Kavanagh wrote:
>> How to do we handle specs that have slipped through the cracks
>> and did not make it for Juno?
>
> Rebase the proposal so it is under the 'kilo' directory path
> instead
On Thu, Aug 28, 2014 at 8:30 AM, Michael Still wrote:
> For nova we haven't gotten around to doing this, but it shouldn't be a
> big deal. I'll add it to the agenda for today's meeting.
>
> Michael
>
For Neutron, I have not gone through and removed specs which merged
and haven't made it yet. I'll
For nova we haven't gotten around to doing this, but it shouldn't be a
big deal. I'll add it to the agenda for today's meeting.
Michael
On Thu, Aug 28, 2014 at 2:07 AM, Andreas Scheuring
wrote:
> Hi,
> is it already possible to submit specs (nova & neutron) for the K
> release? Would be great fo
On Thu, Aug 28, 2014 at 11:51:32AM +, Alan Kavanagh wrote:
> How to do we handle specs that have slipped through the cracks
> and did not make it for Juno?
Rebase the proposal so it is under the 'kilo' directory path
instead of 'juno' and submit it for review again. Make sure
to keep the Chang
How to do we handle specs that have slipped through the cracks and did not make
it for Juno?
/Alan
From: Salvatore Orlando [mailto:sorla...@nicira.com]
Sent: August-28-14 9:48 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] Specs
Only if you think a sphinx compile is necessary for the review.
On Thu, Aug 28, 2014 at 1:14 AM, Andreas Scheuring <
scheu...@linux.vnet.ibm.com> wrote:
> Thanks for your feedback.
>
> So I will create a branch for my bp, add the kilo folder and commit it
> together with my spec.
>
> To get sphi
Thanks for your feedback.
So I will create a branch for my bp, add the kilo folder and commit it
together with my spec.
To get sphinx running I also had to make changes to the toc tree in
nova-specs/doc/source/index.rst
I will also commit this change within my branch, right?
thanks,
Andreas
I think it's ok to submit specs for Kilo - mostly because it would be a bit
pointless submitting them for Juno!
Salvatore
On 28 August 2014 09:26, Kevin Benton wrote:
> You could just make the kilo folder in your commit and then rebase it once
> Kilo is open.
>
>
> On Thu, Aug 28, 2014 at 12:0
You could just make the kilo folder in your commit and then rebase it once
Kilo is open.
On Thu, Aug 28, 2014 at 12:07 AM, Andreas Scheuring <
scheu...@linux.vnet.ibm.com> wrote:
> Hi,
> is it already possible to submit specs (nova & neutron) for the K
> release? Would be great for getting early
Hi,
is it already possible to submit specs (nova & neutron) for the K
release? Would be great for getting early feedback and tracking
comments. Or should I just commit it to the juno folder?
Thanks,
Andreas
___
OpenStack-dev mailing list
OpenStack-de
16 matches
Mail list logo
