Hi all,
thanks for the explanation.
Can you also explain how does neutron team use blueprints? how it overlaps
with RFE bugs?
On Mon, Dec 7, 2015 at 6:40 PM, Sean M. Collins wrote:
> On Mon, Dec 07, 2015 at 12:18:29PM EST, Carl Baldwin wrote:
> > On Fri, Dec 4, 2015 at
On 08/12/15 10:04, Mathieu Rohon wrote:
Hi all,
thanks for the explanation.
Can you also explain how does neutron team use blueprints? how it overlaps with
RFE bugs?
Hi Mathieu,
This is all documented, in principle, at
http://docs.openstack.org/developer/neutron/policies/blueprints.html.
On 07/12/15 17:42, Sean M. Collins wrote:
> On Mon, Dec 07, 2015 at 12:18:29PM EST, Carl Baldwin wrote:
>> On Fri, Dec 4, 2015 at 12:22 PM, Henry Gessau wrote:
>>> 1. RFE: "I want X"
>>> 2. Spec: "I plan to implement X like this"
>>> 3. devref: "How X is implemented and how to
> From: Henry Gessau <ges...@gmail.com>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@lists.openstack.org>
> Date: 12/04/2015 02:23 PM
> Subject: Re: [openstack-dev] [neutron] Multiple locations for
> documenta
On Tue, Dec 08, 2015 at 09:03:10AM EST, Mike Spreitzer wrote:
> Lots cheers from me too. Let me add one thing: "the spec is not
> maintained" is a remaining process bug. A spec by itself is a very useful
> thing. It is the first thing to read when trying to understand the
> implementation.
On Mon, Dec 07, 2015 at 12:18:29PM EST, Carl Baldwin wrote:
> On Fri, Dec 4, 2015 at 12:22 PM, Henry Gessau wrote:
> > 1. RFE: "I want X"
> > 2. Spec: "I plan to implement X like this"
> > 3. devref: "How X is implemented and how to extend it"
> > 4. OS docs: "API and guide for
On Fri, Dec 4, 2015 at 12:22 PM, Henry Gessau wrote:
> 1. RFE: "I want X"
> 2. Spec: "I plan to implement X like this"
> 3. devref: "How X is implemented and how to extend it"
> 4. OS docs: "API and guide for using X"
>
> Once X is implemented I don't want to have to go to 1 or
On 04/12/15 19:24, Henry Gessau wrote:
> Sean M. Collins wrote:
>> I've noticed that a lot of features are now being documented as RSTs
>> inside of devref. Like the following:
>>
>> https://review.openstack.org/#/c/251859/
>>
>> But there are lots already present. Can someone
On 4 December 2015 at 11:22, Henry Gessau wrote:
> Sean M. Collins wrote:
> > I've noticed that a lot of features are now being documented as RSTs
> > inside of devref. Like the following:
> >
> > https://review.openstack.org/#/c/251859/
> >
> > But there
2015-12-05 8:40 GMT+09:00 Armando M. :
>
>
> On 4 December 2015 at 11:22, Henry Gessau wrote:
>>
>> Sean M. Collins wrote:
>> > I've noticed that a lot of features are now being documented as RSTs
>> > inside of devref. Like the following:
Sean M. Collins wrote:
> I've noticed that a lot of features are now being documented as RSTs
> inside of devref. Like the following:
>
> https://review.openstack.org/#/c/251859/
>
> But there are lots already present. Can someone point out to me what the
> criteria is for
Hi,
I've noticed that a lot of features are now being documented as RSTs
inside of devref. Like the following:
https://review.openstack.org/#/c/251859/
But there are lots already present. Can someone point out to me what the
criteria is for these documents? I am a little confused about the
12 matches
Mail list logo