Launchpad logo and name.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index ][Thread Index ]

Re: [Launchpad-users] Launchpad 10.01: bug heat and anonymous API access



2010/1/28 Matthew Revell <matthew.revell@xxxxxxxxxxxxx>:
> Bug heat
> ---------
>
> You can get extra help in judging a bug's significance by using Launchpad's
> new bug heat measure.
>
> In the top-right of bug pages, and in a new column on bug listings, you'll see
> four flame icons. The more of those flames are lit, the "hotter" the bug is.
>
> Launchpad measures a bug's heat depending on how many people are subscribed,
> whether it’s a security issue, how many people have marked the bug as
> affecting them, and so on.

This doesn't seem to be producing any results for most projects at the
moment.  I'm told this is due to two problems:

1- heat is scaled across the whole of lp, and no other bug in all of
free software is as important as the flash plugin crashing ;-)
2- the script to update it is not running?

I'm sure they'll be fixed shortly.

> In bug listings, there's a new sticking plaster icon that shows you which bugs
> have a patch attached.

It's really cute.
> Leonard blogs that:
>
>  Your launchpadlib scripts can now get read-only access to the Launchpad web
>  service API without going through any authorization process. Previously,
>  to authorize your script, you had to open a web page in the end-user's web
>  browser and get the user to click a button. Now, you only have to go through
>  that process if you want to access someone's private data or modify the
>  Launchpad dataset on their behalf.

That's great, it saves a hassle for readonly scripts.

-- 
Martin <http://launchpad.net/~mbp/>



This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.

(Formatted by MHonArc.)