registry team mailing list archive

[Eric Day <613076@xxxxxxxxxxxxxxxxxx>]

Hi Jay!

We had a discussion on IRC yesterday about all this because some folks
were still unsure what blueprints are for (other project management
tools just give you 'issues' or 'bugs' where everything is merged). In
the future tasks like this will be entered as blueprints, but for
these it's probably not worth the time to move them. We won't have
dependencies, but I don't think we really need them for this set.

-Eric

On Thu, Aug 05, 2010 at 02:48:22PM -0000, Jay Pipes wrote:
> On Thu, Aug 5, 2010 at 10:11 AM, Michael Gundlach
> <613076@xxxxxxxxxxxxxxxxxx> wrote:
> > All the other API feature requests are entered as bugs,
> 
> Yes, I noticed...
> 
> > but if you still
> > think this should be a blueprint, feel free to make one and link to it from
> > here.
> 
> Blueprints are for feature requests, particularly requests that are
> related to each other, so you can, for instance, see the relationship
> between tasks and their dependencies.  For example:
> 
> https://blueprints.launchpad.net/drizzle/+spec/replication
> 
> By entering all of these as bugs, there's no way to tell the
> relationship or dependencies between the tasks :(
> 
> I'll go ahead and gradually move these all over to blueprints, where
> they can be properly managed in milestones.
> 
> > Though it may be that closing this bug doesn't take enough design to
> > warrant a blueprint (like, we parse out the .json/.xml suffix or content
> > type, and hand a dict of response data to a json spitter outer or xml
> > spitter outer.)
> 
> The amount of time needed to close/complete something has little to do
> with whether it is a bug or a blueprint.
> 
> -jay
> 
> > On Tue, Aug 3, 2010 at 3:40 PM, Jay Pipes <613076@xxxxxxxxxxxxxxxxxx>
> > wrote:
> >
> >> This should really be a blueprint...
> >>
> >> --
> >> Support JSON or XML in API
> >> https://bugs.launchpad.net/bugs/613076
> >> You received this bug notification because you are a direct subscriber
> >> of the bug.
> >>
> >> Status in OpenStack Compute (Nova): New
> >>
> >> Bug description:
> >> See http://docs.rackspacecloud.com/servers/api/cs-bindguide-latest.pdfpage 8.
> >>
> >> To unsubscribe from this bug, go to:
> >> https://bugs.launchpad.net/nova/+bug/613076/+subscribe
> >>
> >
> >
> > Confidentiality Notice: This e-mail message (including any attached or
> > embedded documents) is intended for the exclusive and confidential use of the
> > individual or entity to which this message is addressed, and unless otherwise
> > expressly indicated, is confidential and privileged information of Rackspace.
> > Any dissemination, distribution or copying of the enclosed material is prohibited.
> > If you receive this transmission in error, please notify us immediately by e-mail
> > at abuse@xxxxxxxxxxxxx, and delete the original message.
> > Your cooperation is appreciated.
> >
> > --
> > Support JSON or XML in API
> > https://bugs.launchpad.net/bugs/613076
> > You received this bug notification because you are a member of Nova
> > Bugs, which is subscribed to OpenStack Compute (nova).
> >
> > Status in OpenStack Compute (Nova): New
> >
> > Bug description:
> > See http://docs.rackspacecloud.com/servers/api/cs-bindguide-latest.pdf page 8.
> >
> >
> >
> 
> -- 
> Support JSON or XML in API
> https://bugs.launchpad.net/bugs/613076
> You received this bug notification because you are a member of Nova
> Bugs, which is subscribed to OpenStack Compute (nova).
> 
> Status in OpenStack Compute (Nova): New
> 
> Bug description:
> See http://docs.rackspacecloud.com/servers/api/cs-bindguide-latest.pdf page 8.
>

-- 
Support JSON or XML in API
https://bugs.launchpad.net/bugs/613076
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.