James Westby wrote:
> On Wed Dec 09 05:30:33 UTC 2009 Jonathan Lange wrote:
> That's fair enough though. We need to be able to access the info. Imagine
> if you were told that you weren't allowed to get the full list of bugs filed
> against LP, except by individually querying the bugs filed against it by
> every LP user in turn. Silly, I know, but we need this information.
I think you're assuming that +activereviews is only way to find this
information in bulk. For other branch listings, we have a +merges page
as well, which presents all the same code reviews as +activereviews (and
more), organized differently and with batching. I think that would be
much more suitable that +activereviews for this purpose.
> That would probably cause more load anyway, as we do the loops to extract
> the full list for display elsewhere.
In addition to load, +activereviews would cause database timeouts. Even
if we provided +activereviews, it's unlikely it would ever work.
Looping is bad, but it would actually work, so it would be better than
+activereviews.
>> >From a user PoV, we don't want to have a page of possible things to do
>> that can practically grow without bound. We already have something like
>> that on the bug tracker, and it's not terribly popular :P
>
> That we can work on. We have plans for LP external tools to help with things
> like this. Some of the knowledge of that can feed back in to LP, and help
> to design pages that show the user the most relevant things to them.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
James Westby wrote:
> On Wed Dec 09 05:30:33 UTC 2009 Jonathan Lange wrote:
> That's fair enough though. We need to be able to access the info. Imagine
> if you were told that you weren't allowed to get the full list of bugs filed
> against LP, except by individually querying the bugs filed against it by
> every LP user in turn. Silly, I know, but we need this information.
I think you're assuming that +activereviews is only way to find this
information in bulk. For other branch listings, we have a +merges page
as well, which presents all the same code reviews as +activereviews (and
more), organized differently and with batching. I think that would be
much more suitable that +activereviews for this purpose.
> That would probably cause more load anyway, as we do the loops to extract
> the full list for display elsewhere.
In addition to load, +activereviews would cause database timeouts. Even
if we provided +activereviews, it's unlikely it would ever work.
Looping is bad, but it would actually work, so it would be better than
+activereviews.
>> >From a user PoV, we don't want to have a page of possible things to do
>> that can practically grow without bound. We already have something like
>> that on the bug tracker, and it's not terribly popular :P
>
> That we can work on. We have plans for LP external tools to help with things
> like this. Some of the knowledge of that can feed back in to LP, and help
> to design pages that show the user the most relevant things to them.
We have a per-user page also: /edge.launchpad .net/~james- w/+activereview s
https:/
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAks ft5cACgkQ0F+ nu1YWqI1XuACfUH QE9MrQ5cTkWrg+ iiv49Hdt EDA9R93m6ie2UtK X3
oCYAnj4SUO60h7u
=nJwT
-----END PGP SIGNATURE-----