On 05/14/15 21:04, Boris Pavlovic wrote:
I believe that backlog should be different much simpler then specs.
Agreed. And they are.
Imho Operators don't have time / don't want to write long long specs and
analyze how they are aligned with specs
or moreover how they should be implemented and
On 05/15/2015 07:20 AM, Boris Pavlovic wrote:
John,
So, you can have all details in the spec, or you can have only the
problem statement complete. Its up to you as a submitter how much
detail you want to provide. I would recommend adding rough ideas into
the alternatives
John,
So, you can have all details in the spec, or you can have only the
problem statement complete. Its up to you as a submitter how much
detail you want to provide. I would recommend adding rough ideas into
the alternatives section, and leaving everything else blank except the
problem
Sean,
Adding most features to most projects requires a reasonable conversation
about how that impacts other parts of that project, and other projects
in OpenStack, and how it impacts existing deploys of OpenStack, and
compatibility between OpenStack implementations in the field, especially
as
On 05/14/15 21:04, Boris Pavlovic wrote:
John,
I believe that backlog should be different much simpler then specs.
Imho Operators don't have time / don't want to write long long specs
and analyze how they are aligned with specs
or moreover how they should be implemented and how they impact
Hi,
I was talking with Matt (VW) about how best some large deployment
working sessions could send their requirements to Nova.
As an operator, if you have a problem that needs fixing or use case
that needs addressing, a great way of raising that issue with the
developer community is a Backlog
