api for blueprint tracker

Bug #146389 reported by Brian Murray on 2007-09-28
38
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Guilherme Salgado

Bug Description

Expose blueprints on the webservice API.

A branch which exposes some attributes of ISpecification and IHasSpecifications has landed on devel but it doesn't expose everything that is available. Separate bugs (e.g. bug 682757) should be filed to have these extra bits exposed.

Related branches

Changed in blueprint:
status: New → Triaged
Graham Binns (gmb) wrote :

Now that we have an actual API, this would be the ideal opportunity to expose blueprints through it...

Changed in blueprint:
importance: Undecided → Medium
Curtis Hovey (sinzui) on 2009-05-17
Changed in blueprint:
importance: Medium → Low
tags: added: feature
Matt Zimmerman (mdz) on 2009-11-19
Changed in blueprint:
assignee: nobody → Jonathan Lange (jml)
Changed in blueprint:
assignee: Jonathan Lange (jml) → Andrew Mitchell (ajmitch)
status: Triaged → In Progress
Curtis Hovey (sinzui) on 2010-01-20
Changed in blueprint:
milestone: none → 10.02
Curtis Hovey (sinzui) on 2010-02-26
Changed in blueprint:
milestone: 10.02 → 10.03
Curtis Hovey (sinzui) on 2010-04-02
Changed in blueprint:
milestone: 10.03 → 10.05
Curtis Hovey (sinzui) on 2010-05-31
Changed in blueprint:
milestone: 10.05 → 10.06
Curtis Hovey (sinzui) on 2010-06-25
Changed in blueprint:
milestone: 10.06 → 10.07
Changed in blueprint:
assignee: Andrew Mitchell (ajmitch) → nobody
Curtis Hovey (sinzui) on 2010-08-12
Changed in blueprint:
milestone: 10.08 → 10.09
Curtis Hovey (sinzui) on 2010-08-18
Changed in blueprint:
status: In Progress → Triaged
milestone: 10.09 → none
RJ Skerry-Ryan (rryan) wrote :

This would be great for us on the Mixxx team because we could easily embed a list of our currently active milestone's blueprints on our website's 'Getting Involved' page so our website will stay current with what our main focus of development is without us having to manually change it. Any word on when this might get finished / what we can do to help?

On Thu, 28 Oct 2010 18:39:28 RJ Ryan wrote:
> This would be great for us on the Mixxx team because we could easily
> embed a list of our currently active milestone's blueprints on our
> website's 'Getting Involved' page so our website will stay current with
> what our main focus of development is without us having to manually
> change it. Any word on when this might get finished / what we can do to
> help?

Very shortly I'll be doing some yak shaving on blueprints.

What exactly are you after?

  subscribe

Thierry Carrez (ttx) wrote :

I was considering writing a blueprint API using screenscraping, but this is definitely the right way of doing it :)

Any project that uses blueprints at a large scale needs this. Even if the long-term plan could be to merge blueprints and bugs, I still think there is value in the short/mid-term to provide such an API.

Changed in blueprint:
assignee: nobody → Guilherme Salgado (salgado)
importance: Low → High
milestone: none → 10.12
status: Triaged → In Progress
Robert Collins (lifeless) wrote :

Hi Salgado, I haven't checked the branch yet, but could you make sure
its only exposed in devel? Theres no sense putting it straight into
long term support if we're going to be refactoring things in the short
term.

Thanks,
Rob

description: updated
tags: added: qa-needstesting
Changed in blueprint:
status: In Progress → Fix Committed
Guilherme Salgado (salgado) wrote :

This has been QAed and is working fine with the exception of the issue reported on bug 683106. I think that's not a big deal and so am tempted to mark this as qa-ok if nobody objects.

tags: added: qa-ok
removed: qa-needstesting

qa-ok it if:
 - its ok to deploy

-Rob

Curtis Hovey (sinzui) on 2010-12-08
Changed in blueprint:
status: Fix Committed → Fix Released
Jay Pipes (jaypipes) wrote :

"if we're going to be refactoring things in the short term."

Does anyone have a link to something that describes the refactoring plans for the short term?

Thanks,
jay

Robert Collins (lifeless) wrote :

dev.launchpad.net/IssueTracker

Jay Pipes (jaypipes) wrote :

Cheers, thanks Robert!

Paul Voccio (pvo) wrote :

What exactly is defined as shortterm for the refactors? This BP for the refactor was written back in '06. Just trying to get a gauge on the timeframe so I can try to work around the issues. Thanks!

Robert Collins (lifeless) wrote :

On Thu, Feb 3, 2011 at 12:25 PM, Paul Voccio <email address hidden> wrote:
> What exactly is defined as shortterm for the refactors? This BP for the
> refactor was written back in '06. Just trying to get a gauge on the
> timeframe so I can try to work around the issues. Thanks!

Its not currently under development; its a fairly important thing -
I'd say 6-12 months.

-Rob

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions