Comment 8 for bug 36645

On Fri, 2006-04-21 at 01:27 +0000, Matthew Paul Thomas wrote:
> Brad, we discussed distro release bugs pages at UBZ. People are going to
> be able to nominate bugs to be fixed in a particular release, and the

This much is obvious, and I'm not suggesting any change to this
workflow.

> distro release bugs page will list those bugs. However, regardless of

...but I am suggesting that having to go to a different part of
Launchpad (leaving the distribution context to go to the distrorelease
context) to see all bugs assigned to Dapper leads users (both newer, and
more experienced) to the following questions when they try to reconcile
the difference between 1. /distros/ubuntu/+bugs and
2. /distros/ubuntu/dapper/+bugs:

 * What's the difference between #1 and #2?

 * Why are there only 50 bugs open on dapper, but 10,000 open on Ubuntu?
(https://launchpad.net/distros/ubuntu/dapper/+bugs is 100% strange.)

 * Why can't I file a bug on dapper? (e.g. expecting that if +bugs
works, +filebug should work in both places, and being annoyed when they
get kicked back to the distro filebug page in this case.)

etc. Examples:

https://launchpad.net/products/malone/+bug/28710
https://launchpad.net/products/malone/+bug/32795

Can you think of good reasons for why bugs targeted to specific releases
can't be listed through using a simple search criterion added to
+bugs-advanced-search?

One argument could be that we might also develop special release
management reports and, I agree, that would be nice, but I still don't
see why that would mean having to force the user out of the distro
context and into the distrorelease one.