Project +index timesout
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Brad Crittenden | ||
Bug Description
The obvious problem for a large projects like the gnome project is the the number of products and the number of milestones. The milestones are insane; the page is intended to be a summary of interesting things about the product, not details from 10 years ago. We want to limit the milestones to the most recent active ones and releases. I am not sure if limiting the number will fix the performance issue.
I prefer not to limit the number of products listed. If we do, we need to provide either a list of all products or use AJAX to append the remaining projects to the list. Oh, we have a check in the view and template that changes the layout if there are many projects. we could use ajax to load large lists after the page has loaded like a bug does with subscribers.
Related branches
- Edwin Grubbs (community): Approve (code)
- Martin Albisetti (community): Approve (ui)
-
Diff: 73 lines2 files modifiedlib/lp/registry/stories/project/xx-project-index.txt (+1/-10)
lib/lp/registry/templates/project-index.pt (+4/-23)
| Changed in launchpad-registry: | |
| assignee: | nobody → Brad Crittenden (bac) |
| Changed in launchpad-registry: | |
| status: | Triaged → In Progress |
| Brad Crittenden (bac) wrote | #1 |
| Brad Crittenden (bac) wrote | #2 |
| Changed in launchpad-registry: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad-registry: | |
| status: | Fix Committed → Fix Released |
Having series and milestone information for each project on the project group page doesn't make sense. The user will want to go to the project page for more detailed information in context. Removing that information should eliminate the timeouts for large projects.
See https:/